Re: [PATCH] Add shell-quasiquote.

[Random832]

Eli Zaretskii <address@hidden> writes:
>> From: Random832 <address@hidden>
>> what is an unusual shell
>
> Any shell that is not the "system's standard shell" is unusual.  I
> thought the text made that clear; if not, please suggest how to
> clarify it (without having an exhaustive list of shells, which would
> be a maintenance burden).

It works on shells that share quoting rules with POSIX, and it works
on MS-DOS, and it works on MS Windows with the assumption that
cmdproxy or any shell listed in w32-system-shells uses the same
rules as cmd.exe and that any other shell uses POSIX semantics.

This gives people a good starting point for understanding what is
"unusual" and what is not, (i.e. bash, ksh, and zsh are not unusual,
even if they are not the system shell) without requiring an
exhaustive list.

>> And I know there's nothing to be done for it, but the fact that it
>> does not have any way to escape wildcards is concerning.
>
> Sorry, I don't follow: in what situation do you think the wildcards
> cannot be escaped?  Are you still talking about MS-Windows?

Yes, sorry. A typical Windows program (at least, one compiled with
MSVC's setargv.obj) will try to interpret wildcards in any part of
CommandLineToArgv's result which contains a ? or * character, with
no provision to prevent it from doing so. (In particular, double
quotes have no effect).