B20: @arg expansion change problem
Christopher G. Faylor
cgf@cygnus.com
Thu Nov 26 18:14:00 GMT 1998
In article <365D84A9.7F6F.cygnus.gnu-win32@hragir.aua.am>,
Jan <jssr@geocities.com> wrote:
>Up to beta19, an argument starting with '@'
>always was considered a usual filename.
>Now in beta20, '@arg' is a filename if 'arg'
>isn't a file, or the content of 'arg' if 'arg'
>is a file.
>
>ex:
> rm a
> touch @a ->'@a' created
> rm @a
> echo e f g > a
> touch @a ->'e','f','g' created instead of '@a'
> this wasn't the case in pre-b20.
>
>As I use make for several dos/windows compilers,
>I need a way to tunnel the '@' through command lines
>without them erroneously getting expanded, should
>the conflicting '@'-less files exist.
>
>Is there a recommended solution for this? Or did I miss
>some environment variable? CYGWIN= noglob at least didn't
>help, and besides I still want the usual *,? wildcards expanded.
Unfortunately this is a change that was requested by our customers. The
obvious workaround is to use ./@file . There is no CYGWIN setting to
control this.
--
cgf@cygnus.com
http://www.cygnus.com/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
More information about the Cygwin
mailing list