nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-09 17:38:00 +00:00
Code Issues Projects Releases Wiki Activity

Docs: use less personalised example Windows prompts.

Browse Source 
The previous prompts were part of transcripts pasted directly from a
particular historical cmd session, but that's no reason to keep them
lying around confusingly, especially since we keep regenerating some
of those transcripts outside that historical context. Replace them all
with nice simple C:\> which shouldn't confuse anyone with extraneous
detail.
This commit is contained in:
Simon Tatham 2020-06-21 16:34:09 +01:00
parent 371c7d12f5
commit f955300576
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/plink.but
View File

@ -39,7 +39,7 @@ Once you've got a console window to type into, you can just type
version of Plink you're using, and gives you a brief summary of how to
use Plink:
\c Z:\sysosd>plink
\c C:\>plink
\c Plink: command-line connection utility
\c Release 0.73
\c Usage: plink [options] [user@]host [command]
@ -100,7 +100,7 @@ Once this works, you are ready to use Plink.
To make a simple interactive connection to a remote server, just
type \c{plink} and then the host name:
\c Z:\sysosd>plink login.example.com
\c C:\>plink login.example.com
\c
\c Debian GNU/Linux 2.2 flunky.example.com
\c flunky login:
@ -117,7 +117,7 @@ In order to connect with a different protocol, you can give the
command line options \c{-ssh}, \c{-telnet}, \c{-rlogin} or \c{-raw}.
To make an SSH connection, for example:
\c Z:\sysosd>plink -ssh login.example.com
\c C:\>plink -ssh login.example.com
\c login as:
If you have already set up a PuTTY saved session, then instead of
@ -125,7 +125,7 @@ supplying a host name, you can give the saved session name. This
allows you to use public-key authentication, specify a user name,
and use most of the other features of PuTTY:
\c Z:\sysosd>plink my-ssh-session
\c C:\>plink my-ssh-session
\c Sent username "fred"
\c Authenticating with public key "fred@winbox"
\c Last login: Thu Dec 6 19:25:33 2001 from :0.0
@ -196,18 +196,18 @@ Once you have done all this, you should be able to run a remote
command on the SSH server machine and have it execute automatically
with no prompting:
\c Z:\sysosd>plink login.example.com -l fred echo hello, world
\c C:\>plink login.example.com -l fred echo hello, world
\c hello, world
\c
\c Z:\sysosd>
\c C:\>
Or, if you have set up a saved session with all the connection
details:
\c Z:\sysosd>plink mysession echo hello, world
\c C:\>plink mysession echo hello, world
\c hello, world
\c
\c Z:\sysosd>
\c C:\>
Then you can set up other programs to run this Plink command and
talk to it as if it were a process on the server machine.

2
doc/pscp.but
View File

@ -37,7 +37,7 @@ Once you've got a console window to type into, you can just type
version of PSCP you're using, and gives you a brief summary of how to
use PSCP:
\c Z:\owendadmin>pscp
\c C:\>pscp
\c PuTTY Secure Copy client
\c Release 0.73
\c Usage: pscp [options] [user@]host:source target