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.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 Subject: RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4 In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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: > 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/