Community
Participate
Working Groups
Build ID: TM 3.1.1 As an embedded developer, I'd like to always see my serial target console in a Terminal. When I quit and restart workbench, I'd like the previous serial Terminal session to automatically reconnect, such that I don't have to connect manually. Acceptance Criteria: -------------------- - Serial connections in visible terminal views should try to re-connect automatically - The reconnect must not impact performance or stability of the rest of WB - If reconnect fails, Workbench must not hang - If automatic reconnect fails, the error should only be printed into the Terminal -- no error dialog should impact Workbench startup. Notes and Constraints: ---------------------- - For connection types that request a password on connect, an automatic reconnect on start does not seem appropriate since a dialog asking for password would be disruptive. On the other hand, if user explicitly requested an auto-reconnect we should honor that. - It is OK to not reconnect invisible terminal views (in other perspectives). - When auto-reconnect fails, then on next quit+restart it is OK to not reconnect again (since previous state was not connected). Implementation Ideas: --------------------- - This is specifically requested for connections that "monitor" something. Typically Serial, but could also be Telnet to a Port Replicator, or ssh in case of a Tunnel. - The connection must have been made to request reconnect on start. - I think that a new checkbox in the connection settings ("Reconnect on Start") should be appropriate. In case the connection is "hidden" in a perspective or terminal tab, it will not reconnect.
CQ:WIND00167225
This is fixed with the Target Explorer "Terminals" view, the dedicated successor of the current TM "Terminal" view. Should be marked fixed once the "Terminal" view got replaced by the "Terminals" view (Kepler?).
The Terminal component of the Eclipse Ecosystem has a new home. The Terminal is now part of the Eclipse CDT project[1]. This change means a new Git repo[2], P2 site[3] and Bugzilla component. The terminal will continue to be delivered as part of the quarterly Simultaneous Release of Eclipse as well. The marketplace entry[4] had not been updated in a few years. It will once again install the latest release of the terminal on the latest release of the whole IDE (currently 2020-03). If this bug is no longer relevant, please feel free to comment or close the bug. If you can confirm if this issues still occurs in the latest release please do let me know in a comment. [1] https://wiki.eclipse.org/CDT/User/NewIn911 [2] https://git.eclipse.org/c/cdt/org.eclipse.cdt.git (in the terminal directory) [3] current release is 9.11 - P2 site https://download.eclipse.org/tools/cdt/releases/9.11/ [4] https://marketplace.eclipse.org/content/tm-terminal (This comment was added to all open terminal bugs along with changing the Product/component pair to CDT/terminal.)
