From: js AT hragir DOT aua DOT am (Jan)
Subject: Re: B20: @arg expansion change problem
30 Nov 1998 20:27:36 -0800
Message-ID: <3662BA5B.3446.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

>js AT hragir DOT aua DOT am wrote, and <cgf AT cygnus DOT com answered:
>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

<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.

Sorry, this workaround won't really help. The dos compilers use an
argument starting with @ for exactly the same thing you try to emulate,
but without really expanding it into the command line. This is needed
because of the DOS limit of 128 command line chars. A ./@file won't be
expanded by them, and @file now creates too long command lines.

An environment var for controlling this (or registry or... or...) seems
kind of necessary for all those who use cygwin together with older SW.
Shouldn't be impossible to do, should it? I wouldn't mind the default
being "expand '@'", so those who wanted the change wouldn't even notice
that step backwards...

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".