> Quoting is a solved problem, including quoting quotes.
Bwa-ha-ha-ha!. Hee. Giggle, Snort. Oh, dear lord, that one deserved a
"coffee and cats" warning. The handling of syntactically significant
characters, such as quotes, slashes, single quotes, and spaces is a
very common cross-platform problem and multiple tool problem. There
are individual tools that do it well. Many, many casually written
access control, hook-scripts, and and build scripts do not. And with
so many interpreters having different syntax for quote handling, it
can actually be impossible for one script to hand off the right number
of levels of quoting to another tool several layers deeper.
On Mon, Nov 18, 2013 at 10:33 AM, Andreas Krey <a.krey_at_gmx.de> wrote:
> On Mon, 18 Nov 2013 07:11:40 +0000, Nico Kadel-Garcia wrote:
>> Brother, unweaving the quotes is its own problem. You see, most
>> filesystems allow single quotes and double quotes in the filenames
>> themselves. Hilarity will ensue.
>
> Quoting is a solved problem, including quoting quotes.
>
> Using newlines a command argument separator because there may be spaces
> in files names is a regression from accepted CLI design, and doesn't
> even solve the problem of newlines in file name which filesystems also
> allow. Besides, hilarity also ensues there when a file happens to be named
> 'rm'.
>
> Andreas
>
> --
> "Totally trivial. Famous last words."
> From: Linus Torvalds <torvalds@*.org>
> Date: Fri, 22 Jan 2010 07:29:21 -0800
Received on 2013-11-19 04:13:57 CET