-\versionid $Id: config.but,v 1.23 2001/12/29 17:21:26 simon Exp $
+\versionid $Id: config.but,v 1.26 2002/02/24 15:25:19 simon Exp $
\C{config} Configuring PuTTY
be empty, this problem should go away, but doing so might cause
other problems.
+Note that this is \e{not} the feature of PuTTY which the server will
+typically use to determine your terminal type. That feature is the
+\q{Terminal-type string} in the Connection panel; see
+\k{config-termtype} for details.
+
\S{config-localecho} \q{Local echo}
\cfg{winhelp-topic}{terminal.localecho}
This mechanism currently only covers ASCII characters, because it
isn't feasible to expand the list to cover the whole of Unicode.
+Character class definitions can be modified by control sequences
+sent by the server. This configuration option only controls the
+\e{default} state. If you modify this option in mid-session using
+\q{Change Settings}, you will need to reset the terminal (see
+\k{reset-terminal}) before the change takes effect.
+
\H{config-colours} The Colours panel
The Colours panel allows you to control PuTTY's use of colour.
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}
+\S{config-telnetnl} \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
+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.