Re: .ONESEHLL not working as expected in 3.82

[Eli Zaretskii]

> From: Paul Smith <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Sat, 27 Apr 2013 12:54:10 -0400
> 
> On Sat, 2013-04-27 at 19:17 +0300, Eli Zaretskii wrote:
> > The .ONESHELL feature is now supported on MS-Windows, for the default
> > Windows shell (cmd.exe) or compatible replacements, in the development
> > version (commit e56aad4).
> 
> Nice!

I see you followed this up with a commit (30843de) which moved code
around that deals with the one_shell use case.  What was the reason
for that change?  I think it breaks the use case where a Unixy shell
is used on MS-Windows under .ONESHELL; this used to work before.

The code block that you moved is needed on MS-Windows as well, when
the shell passes the is_bourne_compatible_shell test.