From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Robertson, Jason V" <jason.v.robertson@intel.com>
To: gnu-win32@cygnus.com
Subject: Asterisk expansion...
Date: Thu, 23 Jul 1998 15:30:00 -0000
Message-id: <7BEBE893ABDFD111AC3F00A0C96B159F5C4CD6@FMSMSX32>
X-SW-Source: 1998-07/msg00502.html

Hi,

There seems to be an inconsistency in how * is interpreted.  When you
run, say, 'echo.exe' from the commandline you get the following:
C:> echo *.*
<Contents of C: are listed>
C:> echo \*.\*
\*.\*

So why does it expand the glob in the first instance, and not unescape
them in the second?  And doesn't this mean it's impossible to echo the
string:
*.*
from cmd?

Running from sh behaves as expected:
$ echo *.*
<contents of pwd are listed>
$ echo \*.\*
*.*

Any ideas?  The reason this is causing problems is that we have a
wrapper around these binaries and it's clueless as to what's expected of
it because it seems indeterminate with respect to commandline expansion.
Is there some hook whereby the tools know if they're being run from
another Cygnus tool so they don't expand the command line?

Thanks,
Jason
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".