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

From: Eli Zaretskii <[email-masked]>
Date: Tue, 17 Jan 2012 07:11:18 +0200

> Date: Mon, 16 Jan 2012 22:45:50 +0100
> From: Lars Ljung <[email-masked]>
> 
> The function eshell-invoke-batch-file expects that
> eshell-windows-shell-file points to something with the behaviour of
> cmd.exe. Currently it defaults to the path to cmdproxy.exe (the default
> value of shell-file-name), which will not work properly.

Why doesn't it work properly?  Can you give a simple test case where
it fails, and explain why?

Thanks.