X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/putty/blobdiff_plain/eee63b77cd283f43234d3a7884ec658fa7dc8778..827b76b3234c644c47be741cabf3d352ba2862bd:/doc/config.but?ds=inline diff --git a/doc/config.but b/doc/config.but index 646b5712..5387a8a3 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.23 2001/12/29 17:21:26 simon Exp $ +\versionid $Id: config.but,v 1.28 2002/03/09 11:47:39 simon Exp $ \C{config} Configuring PuTTY @@ -330,6 +330,11 @@ multiple times at the keyboard. If you set the answerback string to 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} @@ -464,8 +469,11 @@ they send \c{ESC OA} through to \c{ESC OD}. Application Cursor Keys mode can be turned on and off by the server, depending on the application. PuTTY allows you to configure the -initial state, and also allows you to disable application mode -completely. +initial state. + +You can also disable application cursor keys mode completely, using +the \q{Features} configuration panel; see +\k{config-features-application}. \S{config-appkeypad} Controlling Application Keypad mode @@ -489,8 +497,11 @@ function key. This is unavoidable. Application keypad mode can be turned on and off by the server, depending on the application. PuTTY allows you to configure the -initial state, and also allows you to disable application mode -completely. +initial state. + +You can also disable application keypad mode completely, using the +\q{Features} configuration panel; see +\k{config-features-application}. \S{config-nethack} Using NetHack keypad mode @@ -636,6 +647,106 @@ constitute an overload, how short a time period they have to arrive in to do so, and how much silent time is required before the overload feature will deactivate itself. +\H{config-features} The Features panel + +PuTTY's terminal emulation is very highly featured, and can do a lot +of things under remote server control. Some of these features can +cause problems due to buggy or strangely configured server +applications. + +The Features configuration panel allows you to disable some of +PuTTY's more advanced terminal features, in case they cause trouble. + +\S{config-features-application} Disabling application keypad and cursor keys + +\cfg{winhelp-topic}{features.application} + +Application keypad mode (see \k{config-appkeypad}) and application +cursor keys mode (see \k{config-appcursor}) alter the behaviour of +the keypad and cursor keys. Some applications enable these modes but +then do not deal correctly with the modified keys. You can force +these modes to be permanently disabled no matter what the server +tries to do. + +\S{config-features-mouse} Disabling \cw{xterm}-style mouse reporting + +\cfg{winhelp-topic}{features.mouse} + +PuTTY allows the server to send control codes that let it take over +the mouse and use it for purposes other than copy and paste. +Applications which use this feature include the text-mode web +browser \c{links}, the Usenet newsreader \c{trn} version 4, and the +file manager \c{mc} (Midnight Commander). + +If you find this feature inconvenient, you can disable it using the +\q{Disable xterm-style mouse reporting} control. With this box +ticked, the mouse will \e{always} do copy and paste in the normal +way. + +Note that even if the application takes over the mouse, you can +still manage PuTTY's copy and paste by holding down the Shift key +while you select and paste, unless you have deliberately turned this +feature off (see \k{config-mouseshift}). + +\S{config-features-resize} Disabling remote terminal resizing + +\cfg{winhelp-topic}{features.resize} + +PuTTY has the ability to change the terminal's size and position in +response to commands from the server. If you find PuTTY is doing +this unexpectedly or inconveniently, you can tell PuTTY not to +respond to those server commands. + +\S{config-features-altscreen} Disabling switching to the alternate screen + +\cfg{winhelp-topic}{features.altscreen} + +Many terminals, including PuTTY, support an \q{alternate screen}. +This is the same size as the ordinary terminal screen, but separate. +Typically a screen-based program such as a text editor might switch +the terminal to the alternate screen before starting up. Then at the +end of the run, it switches back to the primary screen, and you see +the screen contents just as they were before starting the editor. + +Some people prefer this not to happen. If you want your editor to +run in the same screen as the rest of your terminal activity, you +can disable the alternate screen feature completely. + +\S{config-features-retitle} Disabling remote window title changing + +\cfg{winhelp-topic}{features.retitle} + +PuTTY has the ability to change the window title in response to +commands from the server. If you find PuTTY is doing this +unexpectedly or inconveniently, you can tell PuTTY not to respond to +those server commands. + +\S{config-features-dbackspace} Disabling destructive backspace + +\cfg{winhelp-topic}{features.dbackspace} + +Normally, when PuTTY receives character 127 (^?) from the server, it +will perform a \q{destructive backspace}: move the cursor one space +left and delete the character under it. This can apparently cause +problems in some applications, so PuTTY provides the ability to +configure character 127 to perform a normal backspace (without +deleting a character) instead. + +\S{config-features-charset} Disabling remote character set +configuration + +\cfg{winhelp-topic}{features.charset} + +PuTTY has the ability to change its character set configuration in +response to commands from the server. Some programs send these +commands unexpectedly or inconveniently. In particular, BitchX (an +IRC client) seems to have a habit of reconfiguring the character set +to something other than the user intended. + +If you find that accented characters are not showing up the way you +expect them to, particularly if you're running BitchX, you could try +disabling the remote character set configuration commands. + \H{config-window} The Window panel The Window configuration panel allows you to control aspects of the @@ -1007,6 +1118,10 @@ unchecking the \q{Shift overrides application's use of mouse} checkbox will cause Shift + mouse clicks to go to the server as well (so that mouse-driven copy and paste will be completely disabled). +If you want to prevent the application from taking over the mouse at +all, you can do this using the Features control panel; see +\k{config-features-mouse}. + \S{config-rectselect} Default selection mode \cfg{winhelp-topic}{selection.rect} @@ -1059,6 +1174,12 @@ box below, and press the \q{Set} button. 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. @@ -1293,12 +1414,12 @@ 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} +\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.