Bug 251750 - [terminal][telnet] Improve support for dumb remote socket connections
Summary: [terminal][telnet] Improve support for dumb remote socket connections
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: terminal (show other bugs)
Version: Next   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-22 14:32 EDT by Martin Oberhuber CLA
Modified: 2020-09-04 15:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2008-10-22 14:32:35 EDT
CQ:WIND00139853

There's many interesting remote TCP sockets that the Terminal could be used to drive. Currently, when the TELNET option negotiation fails for a remote socket, we switch off local echo by default. As a result, when the remote doesn't echo, the user cannot see what he types.

Other terminal programs such as PuTTY have an autodetect capability for local echo. I'm not sure how they do it, but one possibility is to detect whether some sent characters are sent back within an acceptable time. Adopting such a scheme may be helpful. I believe that a hardcoded fallback to echo in case of failed TELNET negotiation would not be correct since some sockets might actually echo (and I believe that this is the case for Bootroms such as U-Boot for instance).

Anyways the recommended behavior for dumb remote socket connections is to enable the optional terminal input line (that's what it has been built for). So another nice option would be to display a "user assistance bubble" after connect has determined that no TELNET negotiation happened, which instructs the user to enable the optional input line (or probably auto-enable it). 

The optional input line provides full line editing before actually sending it, has a history and Ctrl+Space completion based on the history so for most dumb socket connections this will be very helpful.
Comment 1 Jonah Graham CLA 2020-05-01 10:10:20 EDT
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.)