Make `Copy all to Clipboard' copy all non-empty lines from the

[u/mdw/putty] / doc / using.but

diff --git a/doc/using.but b/doc/using.but
index 5175215..0ffe58c 100644 (file)
--- a/doc/using.but
+++ b/doc/using.but
@@ -1,4 +1,4 @@
-\versionid $Id: using.but,v 1.14 2003/04/05 11:52:42 simon Exp $
+\versionid $Id: using.but,v 1.19 2004/02/08 00:14:57 jacob Exp $

 
 \C{using} Using PuTTY
 
 
 \C{using} Using PuTTY
 


@@ -32,7 +32,8 @@ server where it will probably cause a process to be interrupted.
 
 Pasting is done using the right button (or the middle mouse button,
 if you have a three-button mouse and have set it up; see
 
 Pasting is done using the right button (or the middle mouse button,
 if you have a three-button mouse and have set it up; see

-\k{config-mouse}). Pressing Shift-Ins has the same effect.
+\k{config-mouse}). (Pressing Shift-Ins, or selecting \q{Paste} from
+the Ctrl+right-click context menu, have the same effect.)

 When you click the right mouse button, PuTTY will
 read whatever is in the Windows Clipboard and paste it into your
 session, \e{exactly} as if it had been typed at the keyboard.
 When you click the right mouse button, PuTTY will
 read whatever is in the Windows Clipboard and paste it into your
 session, \e{exactly} as if it had been typed at the keyboard.


@@ -96,6 +97,10 @@ PuTTY's system menu contains extra program features in addition to
 the Windows standard options. These extra menu commands are
 described below.
 
 the Windows standard options. These extra menu commands are
 described below.
 

+(These options are also available in a context menu brought up
+by holding Ctrl and clicking with the right mouse button anywhere
+in the PuTTY window.)
+

 \S2{using-eventlog} The PuTTY Event Log
 
 If you choose \q{Event Log} from the system menu, a small window
 \S2{using-eventlog} The PuTTY Event Log
 
 If you choose \q{Event Log} from the system menu, a small window


@@ -109,6 +114,14 @@ and hit the Copy button to copy them to the clipboard. If you are
 reporting a bug, it's often useful to paste the contents of the
 Event Log into your bug report.
 
 reporting a bug, it's often useful to paste the contents of the
 Event Log into your bug report.
 

+\S2{using-specials} Special commands
+
+Depending on the protocol used for the current session, there may be a
+submenu of \q{special commands}. These are protocol-specific tokens,
+such as a \q{break} signal, that can be sent down a connection in
+addition to normal data. Currently only Telnet and SSH have special
+commands.
+

 \S2{using-newsession} Starting new sessions
 
 PuTTY's system menu provides some shortcut ways to start new
 \S2{using-newsession} Starting new sessions
 
 PuTTY's system menu provides some shortcut ways to start new


@@ -246,7 +259,8 @@ remote session and have them display their windows on your PC.
 
 Note that if your PC X server requires authentication to connect,
 then PuTTY cannot currently support it. If this is a problem for
 
 Note that if your PC X server requires authentication to connect,
 then PuTTY cannot currently support it. If this is a problem for

-you, you should mail the authors \#{FIXME} and give details.
+you, you should mail the PuTTY authors \#{FIXME} and give details
+(see \k{feedback}).

 
 \H{using-port-forwarding} Using port forwarding in SSH
 
 
 \H{using-port-forwarding} Using port forwarding in SSH
 


@@ -263,7 +277,7 @@ to a port on a remote server, you need to:
 \b Choose a port number on your local machine where PuTTY should
 listen for incoming connections. There are likely to be plenty of
 unused port numbers above 3000. (You can also use a local loopback
 \b Choose a port number on your local machine where PuTTY should
 listen for incoming connections. There are likely to be plenty of
 unused port numbers above 3000. (You can also use a local loopback

-address here; see \k{config-ssh-portfwd} for more details.)
+address here; see below for more details.)

 
 \b Now, before you start your SSH connection, go to the Tunnels
 panel (see \k{config-ssh-portfwd}). Make sure the \q{Local} radio
 
 \b Now, before you start your SSH connection, go to the Tunnels
 panel (see \k{config-ssh-portfwd}). Make sure the \q{Local} radio


@@ -326,6 +340,19 @@ SSH server machine can connect to the forwarded port.) Note that
 this feature is only available in the SSH 2 protocol, and not all
 SSH 2 servers support it (OpenSSH 3.0 does not, for example).
 
 this feature is only available in the SSH 2 protocol, and not all
 SSH 2 servers support it (OpenSSH 3.0 does not, for example).
 

+You can also specify an IP address to listen on. Typically a
+Windows machine can be asked to listen on any single IP address in
+the \cw{127.*.*.*} range, and all of these are loopback addresses
+available only to the local machine. So if you forward (for
+example) \c{127.0.0.5:79} to a remote machine's \cw{finger} port,
+then you should be able to run commands such as \c{finger
+fred@127.0.0.5}. This can be useful if the program connecting to
+the forwarded port doesn't allow you to change the port number it
+uses. This feature is available for local-to-remote forwarded
+ports; SSH1 is unable to support it for remote-to-local ports,
+while SSH2 can support it in theory but servers will not
+necessarily cooperate.
+

 \H{using-rawprot} Making raw TCP connections
 
 A lot of Internet protocols are composed of commands and responses
 \H{using-rawprot} Making raw TCP connections
 
 A lot of Internet protocols are composed of commands and responses


@@ -481,6 +508,11 @@ option instead of \c{-L}:
 \c putty -R 5023:mytelnetserver.myhouse.org:23 -load mysession
 \c plink mysession -R 5023:mytelnetserver.myhouse.org:23
 
 \c putty -R 5023:mytelnetserver.myhouse.org:23 -load mysession
 \c plink mysession -R 5023:mytelnetserver.myhouse.org:23
 

+To specify an IP address for the listening end of the tunnel,
+prepend it to the argument:
+
+\c plink -L 127.0.0.5:23:localhost:23 myhost
+

 To set up SOCKS-based dynamic port forwarding on a local port, use
 the \c{-D} option. For this one you only have to pass the port
 number:
 To set up SOCKS-based dynamic port forwarding on a local port, use
 the \c{-D} option. For this one you only have to pass the port
 number:


@@ -499,7 +531,7 @@ file
 The \c{-m} option performs a similar function to the \q{Remote
 command} box in the SSH panel of the PuTTY configuration box (see
 \k{config-command}). However, the \c{-m} option expects to be given
 The \c{-m} option performs a similar function to the \q{Remote
 command} box in the SSH panel of the PuTTY configuration box (see
 \k{config-command}). However, the \c{-m} option expects to be given

-a file name, and it will read a command from that file. On most Unix
+a local file name, and it will read a command from that file. On most Unix

 systems, you can even put multiple lines in this file and execute
 more than one command in sequence, or a whole shell script.
 
 systems, you can even put multiple lines in this file and execute
 more than one command in sequence, or a whole shell script.