nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-02 12:02:47 -05:00
Code Issues Projects Releases Wiki Activity

Add a configurable option to make Return in Telnet send an ordinary

Browse Source 
^M instead of the Telnet New Line code. Unix-type telnetds don't
care one way or the other; RDB claims some telnetds prefer Telnet
NL; and now someone has found one that can't deal with Telnet NL and
prefers ^M. Sigh.

[originally from svn r1520]
This commit is contained in:
Simon Tatham
2001-12-29 17:21:26 +00:00
parent 69b15bcc90
commit 726f9dde7e
5 changed files with 38 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
doc/config.but
View File

@ -1,4 +1,4 @@
\versionid $Id: config.but,v 1.22 2001/12/15 12:15:24 simon Exp $
\versionid $Id: config.but,v 1.23 2001/12/29 17:21:26 simon Exp $
\C{config} Configuring PuTTY
@ -1293,6 +1293,22 @@ the Telnet special backspace code, and Control-C will send the
Telnet special interrupt code. You probably shouldn't enable this
unless you know what you're doing.
\S{config-telnetkey} \q{Return key sends telnet New Line instead of ^M}
\cfg{winhelp-topic}{telnet.newline}
Unlike most other remote login protocols, the Telnet protocol has a
special \Q{new line} code that is not the same as the usual line
endings of Control-M or Control-J. By default, PuTTY sends the
Telnet New Line code when you press Return, instead of sending
Control-M as it does in most other protocols.
Most Unix-style Telnet servers don't mind whether they receive
Telnet New Line or Control-M; some servers do expect New Line, and
some servers prefer to see ^M. If you are seeing surprising
behaviour when you press Return in a Telnet session, you might try
turning this option off to see if it helps.
\H{config-rlogin} The Rlogin panel
The Rlogin panel allows you to configure options that only apply to