From: js AT hragir DOT aua DOT am (Jan) Subject: Re: B20: @arg expansion change problem 1 Dec 1998 11:50:39 -0800 Message-ID: <3663CADF.274B.cygnus.gnu-win32@hragir.aua.am> Reply-To: jssr AT geocities DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: gnu-win32 AT cygnus DOT com Cc: js AT lorien DOT slab DOT de In article <365D84A9 DOT 7F6F DOT cygnus DOT gnu-win32 AT hragir DOT aua DOT am>, >Jan wrote, and ;Christopher G. Faylor (cgf AT cygnus DOT com) replied: > 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 ; 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. 1. Please excuse the previous, garbled reply which obviously contained unusual quoting chars that confused the mailing system. 2. ./@file won't always help. @file is something older DOS software (msvc, bcc) expands in a way similar to what cygwin32 does, but without interfering with the DOS limit of 128 command line chars. Needless to say, the DOS software doesn't recognize ./@file. 3. At the moment, the only real workaround is avoiding such DOS command lines getting parsed through cygwin32. Sorry, sometimes that's a severe restriction. A possibility to revert to the old behaviour via environment would help very much. If the default is the new behaviour, this shouldn't hurt anybody. js - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".