Subject: Re: bug#10523: 24.0.92; Wrong init value for eshell-windows-shell-file

From: Lars Ljung <[email-masked]>
Date: Tue, 17 Jan 2012 06:53:38 +0100

2012-01-17 06:11, Eli Zaretskii skrev:
> Why doesn't it work properly?  Can you give a simple test case where
> it fails, and explain why?

With cmdproxy.exe it will look like this:

~ $ test.bat arg1 arg2
warning: extra args ignored after 'test.bat'

The warning is printed by cmdproxy.exe and the reason is that the
command gets translated to the following:

cmdproxy.exe /c test.bat arg1 arg2

But cmdproxy.exe expects one single argument after /c, .i.e.
cmdproxy.exe /c "test.bat arg1 arg2". cmd.exe on the other hand uses all
remaining arguments on the command line.

To me it looks like the regexp is used to avoid using cmdproxy.exe, but
it fails because of the extra \\`.

Regards,
Lars Ljung