Link or rename wcmd.exe to cmd.exe?

[Thomas Kho]

On 7/3/06, Chris <chris.kcat at gmail.com> wrote:
> On Sunday 02 July 2006 23:58, you wrote:
> > The case I care about most is:
> > in cron, or ssh'ing in without X forwarding, use wcmd.exe to run a batch
> > file.
> >
> > We need to be able to support both cases.
>
> How about leaving wcmd.exe alone (or renaming it to winecmd.exe), and wait on
> making cmd.exe until a replacement that behaves like Windows' cmd.exe, then?
> You can have both that way. I'm mostly concerned about apps and/or people
> that expect cmd.exe to behave like Windows' version, when Wine's wcmd.exe
> doesn't.

Window's cmd.exe run under Wine seems to do exactly what wcmd.exe
currently does in that it runs in its original terminal without
creating a new console window. Creating the console to host cmd.exe is
likely ouside the scope of cmd.exe.

Also, running cmd.exe from within an instance of cmd.exe in Windows
does not open a new console window--using an existing console, be it
unix or dos, seems to be the right thing to do.

Thomas Kho