Re: .ONESEHLL not working as expected in 3.82

[Eli Zaretskii]

> From: Paul Smith <address@hidden>
> Cc: address@hidden
> Date: Sun, 28 Apr 2013 16:01:05 -0400
> 
> I guess I thought you were writing a batch file,
> then invoking the shell with the batch file name as the command to run.
> E.g., "command.com <batchfile>" vs. "perl <batchfile>" etc.  I am naive
> but it seems like that should work OK even in Windows :-).

It does work, but there's no need to invoke the shell explicitly in
this case.  We just invoke the batch file itself, and Windows invokes
the shell for us.  That way, we save ourselves some trouble, like
formatting the shell switches, quoting the command (could be quite
tricky with Windows shells), etc.

> I guess there are some tricky bits if you sometimes use the command line
> and sometimes a batch file (different shell options might be needed for
> example).

There's no way I know of to pass an arbitrary series of command lines
to a Windows shell, except through a batch file.