Carlos E. R. wrote:
On 2023-03-09 13:41, Per Jessen wrote:
Carlos E. R. wrote:
No, because if the filename contains spaces, for instance, the paste doesn't run.
Must be a failure on your machine. I mean, putting space in filenames is of course a failure by itself, but I have no problem pasting a text with spaces in.
(having just selected the above, then I hit paste.) (2nd paste).
Sigh... you are being obtuse.
Not at all. Maybe re-read what you wrote.
cer@Telcontar:~/tmp/Per> touch "file with spaces" cer@Telcontar:~/tmp/Per> cer@Telcontar:~/tmp/Per> ls SAM_5792-g2.JPG SAM_5794.JPG SAM_5796-cut.JPG SAM_5797.JPG SAM_5798.JPG SAM_5799.JPG Screenshot_20210220-192408.png SAM_5792.JPG SAM_5795.JPG SAM_5796.JPG SAM_5798-cut.JPG SAM_5799-cut.JPG Screenshot_20210220-192408.jpg file with spaces cer@Telcontar:~/tmp/Per> ls -l file with spaces ls: cannot access 'file': No such file or directory ls: cannot access 'with': No such file or directory ls: cannot access 'spaces': No such file or directory
I see that too much exposure to the Obscure File Manager has impacted your knowledge of the Linux command line :-) Let me ask - why did you feel the need to use quotes for the 'touch', but not for the 'ls' ? Just to be able to demonstrate that whitespace is the default field separator on the Linux command line? If I do it: touch file with spaces ls -l file with spaces touch "file with spaces" ls -l "file with spaces" touch file\ with\ spaces ls -l file\ with\ spaces They all work just fine. (different results of course). However, I don't at all see what it has got to do with "because if the filename contains spaces, for instance, the paste doesn't run.". Above I pasted "file with spaces" five times, it worked fine. -- Per Jessen, Zürich (16.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes