I want to copy a file from remote to local system. Now I'm using scp command in linux system. I have some folders or files names are with spaces, when I try to copy that file, it shows the error message: "No such file or directory".
I tried:
scp ael5105@192.168.0.200:'/home/5105/test/gg/Untitled Folder/a/qy.jpg' /var/www/try/
I saw the some reference online but I don't understand perfectly, can any one help on this?
how can I escape spaces in file name or directory names during copying...
works
scp localhost:"f/a\ b\ c" .
scp localhost:'f/a\ b\ c' .
does not work
scp localhost:'f/a b c' .
The reason is that the string is interpreted by the shell before the path is passed to the scp command. So when it gets to the remote the remote is looking for a string with unescaped quotes and it fails
To see this in action, start a shell with the -vx options ie bash -vx
and it will display the interpolated version of the command as it runs it.
"
or single '
work the same Basically you need to escape it twice, because it's escaped locally and then on the remote end.
There are a couple of options you can do (in bash):
scp user@example.com:"'web/tmp/Master File 18 10 13.xls'" .
scp user@example.com:"web/tmp/Master\ File\ 18\ 10\ 13.xls" .
scp user@example.com:web/tmp/Master\\\ File\\\ 18\\\ 10\\\ 13.xls .
scp user@example.com:'$(ls -t | head -1)' .
to get the most recently created file in the server, or scp user@example.com:'dir/*.{xml,pdf}' .
to get all xml and pdf files from a remote directory. In general, I prefer this over having convenience with files that have spaces. Files with spaces are always a bother. -T
. See stackoverflow.com/q/54598689/452614 Also you can do something like:
scp foo@bar:"\"apath/with spaces in it/\""
The first level of quotes will be interpreted by scp and then the second level of quotes will preserve the spaces.
I had huge difficulty getting this to work for a shell variable containing a filename with whitespace. For some reason using:
file="foo bar/baz"
scp user@example.com:"'$file'"
as in @Adrian's answer seems to fail.
Turns out that what works best is using a parameter expansion to prepend backslashes to the whitespace as follows:
file="foo bar/baz"
file=${file// /\\ }
scp user@example.com:"$file"
file="${file//\ /\\\ }"
${file//\ /\\\ }
is better than ${file// /\\ }
? Does that space need escaping for some reason? /home/user/folder/
followed by the file with spaces? I have to enclose the whole thing with double quotes and escaping the one around the $file
doesn't work. file=${file//\\/\\\\};file=${file// /\\ }
export file='"foo bar/baz"' ; scp user@example.com:"$file"
. That way I can avoid the substitution. Maybe that is worth including in the answer. Use 3 backslashes to escape spaces in names of directories:
scp user@host:/path/to/directory\\\ with\\\ spaces/file ~/Downloads
should copy to your Downloads
directory the file
from the remote directory called directory with spaces
.
\\\_
is escaped once to get \_
and then it is escaped another time to get a space _
. I used _
to clearly represent a space. Sorry for using this Linux question to put this tip for Powershell on Windows 10: the space char escaping with backslashes or surrounding with quotes didn't work for me in this case. Not efficient, but I solved it using the "?" char instead:
for the file "tasks.txt Jun-22.bkp" I downloaded it using "tasks.txt?Jun-22.bkp"
scp ael5105@192.168.0.200:/home/5105/test/gg/Untitled?Folder/a/qy.jpg /var/www/try/
the ? does a glob on the remote and will match any character, including a space
I encountered similar issues when trying to copy files from remote paths containing spaces using scp
from within a Bash script.
Here are the solutions I came up with:
Escape paths manually:
scp user@host:'dir\ with\ spaces/file\ with\ spaces' <destination>
scp user@host:"dir\\ with\\ spaces/file\\ with\\ spaces" <destination>
scp user@host:dir\\\ with\\\ spaces/file\\\ with\\\ spaces <destination>
Note: does not require option -T
(see below).
Use double-quoting + option -T
:
scp -T user@host:"'<path-with-spaces>'" <destination>
scp -T user@host:'"<path-with-spaces>"' <destination>
scp -T user@host:"\"<path-with-spaces>\"" <destination>
Note: without option -T
, these commands fail with protocol error: filename does not match request
. The reason for this is discussed in detail here.
Escape path using Bash's printf:
source="<path-with-spaces>"
printf -v source "%q" "${source}"
scp user@host:"${source}" <destination>
One-liner for shell use:
source="<path-with-spaces>"; printf -v source "%q" "${source}"; scp user@host:"${source}" <destination>
Note: works fine without option -T
.
printf
alternative. If the file or folder name is having space in between then you can simply add a black slash '' before the space and then put the whole path inside a single quotation ('') and it should work then.
Example:
Suppose the folder name is 'Test Folder' and it is inside /home/ in remote machine. Then you can access or download the folder using following scp command.
scp -r <user>@<host>:'/home/Test\ Folder' .
I'm new to Linux and I used Kali xD, here how's mine works: From your system to remote server if you want to transfer your file with single or multiple spaces:
$ scp this\ is\ my\ file tryhackme@1.1.1.1:/home/tryhackme
Note that the IP address is only example and the last I type is directory and the dollar sign which is the prompt, the code start with scp.
Also you can specifiy what name you want to that file when it is transfer, ex. /home/tryhackme/file1
or with single or multiple spaces like /home/tryhackme/"this\ is\ new\ file"
.
From remote server to your system, same as above with single or multiple spaces:
$ scp tryhackme@1.1.1.1:/home/tryhackme/"remote\ server\ file" "this is mine now"
Note that you only use backward slash \\
to the file you want to copy, as you can see that the string "this is mine now"
has no \\
because that is the name of the file we want when it transfer to our system and not the file that we want to secure copy (scp). Sorry for my explanation, I hope someone will understand, I hope this helps to someone who needs another solution.
In linux-terminal or cmd if there is any space in path between word you must use quotation ('') ("") mark.
you should something like this :
$ '/home/tryhackme'
not
$ /home/tryhackme
Just stick wildcards in where the spaces should be: 'foo/bar*bar.txt'