Re: [PATCH] Add shell-quasiquote.

[Eli Zaretskii <eliz@gnu.org>]

> From: Random832 <random832@fastmail.com>
> Date: Sun, 18 Oct 2015 15:17:53 -0400
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> >> From: Random832 <random832@fastmail.com>
> >> 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.

Yes, that's a reasonable interpretation of "standard shell" on each of
these operating systems.

> >> 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).

This actually depends on the startup code.  The latest release of
mingw.org's MinGW runtime does allow you to quote wildcard characters.
And on Windows XP and older even the other runtimes allow that.

In any case, this is not an Emacs problem.