Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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.20030312161013.034cbab8@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Wed, 12 Mar 2003 16:13:36 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4 In-Reply-To: References: <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030312153011 DOT 046de318 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 16:00 2003-03-12, Igor Pechtchanski wrote: >On Wed, 12 Mar 2003, Randall R Schulz wrote: > >... > > > >Just got another idea. See if this helps: > > > > > > > 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. > >Randall, > >I believe we *were* talking about stracing the offending program under >cmd.exe... > Igor Igor, Really? Both cases appear in the earlier messages on this thread. Nonetheless, I think that the wider implication of erroneous recipes in the documentation should be pointed out. No? Randall Schulz -- 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/