X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/putty/blobdiff_plain/0d2086c5db1f23869109ba6776cb6d2e6037714c..23fc996adbb32bffe3e6f4fafff53cce8a4192eb:/doc/config.but diff --git a/doc/config.but b/doc/config.but index b7e16acd..d5d03613 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.27 2002/03/06 23:04:20 simon Exp $ +\versionid $Id: config.but,v 1.32 2002/05/11 13:03:47 owen Exp $ \C{config} Configuring PuTTY @@ -380,6 +380,38 @@ this configuration option to override its choice: you can force local line editing to be turned on, or force it to be turned off, instead of relying on the automatic detection. +\S{config-printing} Remote-controlled printing + +\cfg{winhelp-topic}{terminal.printing} + +A lot of VT100-compatible terminals support printing under control +of the remote server. PuTTY supports this feature as well, but it is +turned off by default. + +To enable remote-controlled printing, choose a printer from the +\q{Printer to send ANSI printer output to} drop-down list box. This +should allow you to select from all the printers you have installed +drivers for on your computer. Alternatively, you can type the +network name of a networked printer (for example, +\c{\\\\printserver\\printer1}) even if you haven't already +installed a driver for it on your own machine. + +When the remote server attempts to print some data, PuTTY will send +that data to the printer \e{raw} - without translating it, +attempting to format it, or doing anything else to it. It is up to +you to ensure your remote server knows what type of printer it is +talking to. + +Since PuTTY sends data to the printer raw, it cannot offer options +such as portrait versus landscape, print quality, or paper tray +selection. All these things would be done by your PC printer driver +(which PuTTY bypasses); if you need them done, you will have to find +a way to configure your remote server to do them. + +To disable remote printing again, choose \q{None (printing +disabled)} from the printer selection list. This is the default +state. + \H{config-keyboard} The Keyboard panel The Keyboard configuration panel allows you to control the behaviour @@ -668,6 +700,26 @@ 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} @@ -977,6 +1029,11 @@ the server is interpreted as being in the UTF-8 encoding of Unicode. If you select \q{UTF-8} as a character set you can use this mode. Not all server-side applications will support it. +If you need support for a numeric code page which is not listed in +the drop-down list, such as code page 866, then you should be able +to enter its name manually (\c{CP866} for example) in the list box +and get the right result. + \S{config-cyr} \q{Caps Lock acts as Cyrillic switch} \cfg{winhelp-topic}{translation.cyrillic} @@ -1098,6 +1155,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} @@ -1301,6 +1362,96 @@ types of server. The Nagle algorithm is disabled by default. +\H{config-proxy} The Proxy panel + +The Proxy panel allows you to configure PuTTY to use various types +of proxy in order to make its network connections. The settings in +this panel affect the primary network connection forming your PuTTY +session, but also any extra connections made as a result of SSH port +forwarding (see \k{using-port-forwarding}). + +\S{config-proxy-type} Setting the proxy type + +The \q{Proxy type} radio buttons allow you to configure what type of +proxy you want PuTTY to use for its network connections. The default +setting is \q{None}; in this mode no proxy is used for any +connection. + +\b Selecting \q{HTTP} allows you to proxy your connections through a +web server supporting the HTTP \cw{CONNECT} command, as documented +in \W{http://www.ietf.org/rfc/rfc2817.txt}{RFC 2817}. + +\b Selecting \q{SOCKS} allows you to proxy your connections through +a SOCKS server. + +\b Many firewalls implement a less formal type of proxy in which a +user can make a Telnet connection directly to the firewall machine +and enter a command such as \c{connect myhost.com 22} to connect +through to an external host. Selecting \q{Telnet} allows you to tell +PuTTY to use this type of proxy. + +Note [FIXME] that SOCKS is not yet supported, although it should be +by the time we make our next release. + +\S{config-proxy-exclude} Excluding parts of the network from proxying + +Typically you will only need to use a proxy to connect to non-local +parts of your network; for example, your proxy might be required for +connections outside your company's internal network. In the +\q{Exclude Hosts/IPs} box you can enter ranges of IP addresses, or +ranges of DNS names, for which PuTTY will avoid using the proxy and +make a direct connection instead. + +The \q{Exclude Hosts/IPs} box may contain more than one exclusion +range, separated by commas. Each range can be an IP address or a DNS +name, with a \c{*} character allowing wildcards. For example: + +\c *.example.com + +This excludes any host with a name ending in \c{.example.com} from +proxying. + +\c 192.168.88.* + +This excludes any host with an IP address starting with 192.168.88 +from proxying. + +\c 192.168.88.*,*.example.com + +This excludes both of the above ranges at once. + +\S{config-proxy-auth} Username and password + +If your proxy requires authentication, you can enter a username and +a password in the \q{Username} and \q{Password} boxes. + +Currently these boxes have no effect ( [FIXME] presumably they're +for SOCKS only). + +\S{config-proxy-command} Specifying the Telnet proxy command + +If you are using the Telnet proxy type, the usual command required +by the firewall's Telnet server is \c{connect}, followed by a host +name and a port number. If your proxy needs a different command, +you can enter an alternative here. + +In this string, you can use \c{\\n} to represent a new-line, \c{\\r} +to represent a carriage return, \c{\\t} to represent a tab +character, and \c{\\x} followed by two hex digits to represent any +other character. \c{\\\\} is used to encode the \c{\\} character +itself. + +Also, the special strings \c{%host} and \c{%port} will be replaced +by the host name and port number you want to connect to. To get a +literal \c{%} sign, enter \c{%%}. + +\S{config-proxy-socksver} Selecting the version of the SOCKS protocol + +SOCKS servers exist in two versions: version 5 +(\W{http://www.ietf.org/rfc/rfc1928.txt}{RFC 1928}) and the earlier +version 4. The \q{SOCKS Version} radio buttons allow you to select +which one to use, if you have selected the SOCKS proxy type. + \H{config-telnet} The Telnet panel The Telnet panel allows you to configure options that only apply to @@ -1502,6 +1653,9 @@ version 1 or version 2. \#{FIXME: say something about this elsewhere?} PuTTY will attempt to use protocol 1 if the server you connect to does not offer protocol 2, and vice versa. +If you select \q{2 only} here, PuTTY will only connect if the server +you connect to offers SSH protocol version 2. + \S{config-ssh-macbug} \q{Imitate SSH 2 MAC bug} \cfg{winhelp-topic}{ssh.buggymac}