shell-file-name cmdproxy and shell-command-switch -c

shell-file-name cmdproxy and shell-command-switch -c

[Lennart Borgman]

I see in ediff-patch-file-internal that shell-file-name is cmdproxy and 
shell-command-switch is -c. cmd.exe wants /c. Is there some magic in 
cmdproxy that translates -c to /c or is this a bug?

Re: shell-file-name cmdproxy and shell-command-switch -c

[Eli Zaretskii]

> Date: Wed, 20 Dec 2006 01:31:17 +0100
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> 
> I see in ediff-patch-file-internal that shell-file-name is cmdproxy and 
> shell-command-switch is -c. cmd.exe wants /c. Is there some magic in 
> cmdproxy that translates -c to /c or is this a bug?

Actually, dealing with -c is the main reason why cmdproxy was
originally written.  From the commentary near the beginning of
cmdproxy.c:

   The main function is simply to process the "-c string" option in the
   way /bin/sh does, since the standard Windows command shells use the
   convention that everything after "/c" (the Windows equivalent of
   "-c") is the input string.

So this is not a bug, it's a feature meant to avoid ugly
system-dependent code anywhere where a shell command is invoked by
Emacs.