Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.2.0.9.2.20030312153011.046de318@pop3.cris.com>
X-Sender:	rrschulz AT pop3 DOT cris DOT com
Date:	Wed, 12 Mar 2003 15:34:16 -0800
To:	cygwin AT cygwin DOT com
From:	Randall R Schulz <rrschulz AT cris DOT com>
Subject:	RE: cygwin 1.3.20-1 - strange problems with long command lines
	in nt4
In-Reply-To:	<Pine.GSO.4.44.0303121822530.25867-100000@slinky.cs.nyu.edu
	>
References:	<BC46D442BCFB6340A9BB1CED6766E36E024E702B AT tons2226>
Mime-Version:	1.0

Igor,

At 15:24 2003-03-12, Igor Pechtchanski wrote:
>On Wed, 12 Mar 2003, Willis, Matthew wrote:
>
>...
>
> > which will run when I pass long arguments using bash.exe as my shell. I can
> > also pass long arguments to this program under cmd.exe. The only difference
> > seems to be that bash.exe fully expands argv[0] to the full win32 path name
> > and cmd.exe leaves it as myecho.exe. In both cases I was able to 
> use command
> > lines over 2000 bytes long without problems.
>
>Matt,
>
>Just got another idea.  See if this helps:
><http://cygwin.com/cygwin-ug-net/using-specialnames.html#AEN733>

I believe the @argFileName syntax only works when a non-Cygwin program 
invokes a Cygwin program.

I cannot make the example given in the user guide section you mention 
work as shown (under BASH). It does work when run from CMD.exe.


>     Igor




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -