bug#19817: 24.4; cmdproxy fails on some .exe when given a path argument

[Eli Zaretskii <eliz@gnu.org>]

> Date: Mon, 09 Feb 2015 15:46:12 +0100
> From: Fabio Leimgruber <fabio.leimgruber@web.de>
> CC: 19817@debbugs.gnu.org
> 
> On 2/8/15 8:29 PM, Eli Zaretskii wrote:
> > 
> > You are not supposed to invoke cmdproxy directly, only via Emacs
> > functions that invoke shell commands.  So please show a test case
> > which works with "write" or "write.exe" or "write.test.exe", but fails
> > with "write.test".
> > 
> 
> (defun compile-quoted (command &rest args)
>   "Run `compile' with COMMAND and ARGS quoted.
> 
> Useful if you can not be sure if there are special characters in
> the command or arguments, like `start-process' allows."
>   (let ((compile-command (mapconcat #'shell-quote-argument
>                                     (cons command args)
>                                     " ")))
>     (compile compile-command)))
> 
> (compile-quoted "write" "d:/asdf.txt")
> 
> (compile-quoted "write.test" "d:/asdf.txt")

Thanks, I will look into this.

One question, though: which executable programs should exist in the
current directory for this test case to reproduce the problem?  Is the
answer write.exe and write.test.exe?  (I'm asking because the original
use case seemed to involve a batch file as well, which complicates
things quite a lot.)