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

Tweak the "PSCP filenames with spaces" FAQ.

Browse Source 
These days it's overwhelmingly likely that SFTP will be in use, so deal
with that case first.
This commit is contained in:
Jacob Nevins 2022-05-25 01:16:31 +01:00
parent 7e65b705f1
commit 55b53923d6
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/faq.but
View File

@ -607,9 +607,16 @@ To use PSCP properly, run it from a Command Prompt window. See
\S{faq-pscp-spaces}{Question} \I{spaces in filenames}How do I use
PSCP to copy a file whose name has spaces in?
If PSCP is using the traditional SCP protocol, this is confusing. If
you're specifying a file at the local end, you just use one set of
quotes as you would normally do:
If PSCP is using the newer SFTP protocol (which is usual with most
modern servers), this is straightforward; all filenames with spaces
in are specified using a single pair of quotes in the obvious way:
\c pscp "local file" user@host:
\c pscp user@host:"remote file" .
However, if PSCP is using the older SCP protocol for some reason,
things are more confusing. If you're specifying a file at the local
end, you just use one set of quotes as you would normally do:
\c pscp "local filename with spaces" user@host:
\c pscp user@host:myfile "local filename with spaces"
@ -633,13 +640,6 @@ Instead, you need to specify the local file name in full:
\c c:\>pscp user@host:"\"oo er\"" "oo er"
If PSCP is using the newer SFTP protocol, none of this is a problem,
and all filenames with spaces in are specified using a single pair
of quotes in the obvious way:
\c pscp "local file" user@host:
\c pscp user@host:"remote file" .
\S{faq-32bit-64bit}{Question} Should I run the 32-bit or the
64-bit version?