[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Make CVS (Win32) improperly leaves batch files with -n
From: |
J. David Bryan |
Subject: |
Re: Make CVS (Win32) improperly leaves batch files with -n |
Date: |
Thu, 16 Feb 2006 11:23:45 -0500 |
On Wed, 15 Feb 2006 06:32:04 +0200, you wrote:
>> From: "J. David Bryan" <address@hidden>
>> Date: Tue, 14 Feb 2006 18:54:59 -0500
>> CC: address@hidden
>>
>> Would it be reasonable to condition this on whether "command.com" or
>> "cmd.exe" is the shell?
>
>Quoting in cmd.exe is still very different from a Unixy shell, so
>construct_command_argv_internal will still need lots of cmd-specific
>code fragments, I think.
I've thought about this, and I'm not sure that I understand why quoting
matters. I accept that quoting in "cmd" and "sh" differ. But isn't the
issue whether "make" can pass commands to "cmd" directly or must pass them
via batch files?
In other words, are there commands that cannot be passed to "cmd" as
arguments but that will work if the identical strings are placed in batch
files? If you have an example, that would help me to grasp the issue.
If there aren't, then perhaps the string currently being placed in the
batch file could simply be passed via "cmd /c <string>" instead, at least
when "cmd" is the shell.
-- Dave
- Re: Make CVS (Win32) improperly leaves batch files with -n,
J. David Bryan <=
- Re: Make CVS (Win32) improperly leaves batch files with -n, Eli Zaretskii, 2006/02/16
- Re: Make CVS (Win32) improperly leaves batch files with -n, J. David Bryan, 2006/02/17
- Re: Make CVS (Win32) improperly leaves batch files with -n, Eli Zaretskii, 2006/02/17
- Re: Make CVS (Win32) improperly leaves batch files with -n, J. David Bryan, 2006/02/17
- Re: Make CVS (Win32) improperly leaves batch files with -n, J. David Bryan, 2006/02/18
- Re: Make CVS (Win32) improperly leaves batch files with -n, Eli Zaretskii, 2006/02/18