On 2023-03-09 17:32, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-09 14:26, Per Jessen wrote:
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?
Because the point is that 'mc' automatically generates the escapes.
You can not simply click and paste a filename in the CLI obtained from an "ls" listing, you have to manually do something so that whatever command works.
Not if you know how to use 'ls'. man ls.
I have read it many times...
If you use "-Q" with ls, filenames are listed in quotes, copy&paste works very well.
I had no idea of that. News to me. Never heard of it. Etc. :-p Tried it now. It puts everything in quotes, even the names that do not need it. Consistency? -Q, --quote-name enclose entry names in double quotes --quoting-style=WORD use quoting style WORD for entry names: literal, locale, shell, shell-always, shell-escape, shell-es- cape-always, c, escape (overrides QUOTING_STYLE environment variable) Thousands of times I have copy pasted ls listings and added the quotes manually in an editor. You could have told me this decades ago! :-P
Anyway, very entertaining discussion - especially that it seems to divide people into "love it" or "never heard of it".
:-) I did not know what an OFM was till a few years back, despite using them for decades. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)