RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

On Wed, 12 Mar 2003, Randall R Schulz wrote: > 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 believ

RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

I find that I can successfully pass long args to echo.exe using the @arglist method. It is not too convenient though as using cmd.exe for a shell is pretty awful. And I couldn't get g++ to work under cmd.exe ("The dynamicl link library cygwin1.dll could not be found...") For the time being, I gues

RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

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 C

RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

On Wed, 12 Mar 2003, Randall R Schulz wrote: > 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 unde

RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

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 expand

RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

On Wed, 12 Mar 2003, Willis, Matthew wrote: > > Igor wrote: > > You may be hitting the command-line limit with bash. Try the above with > > cmd.exe. See below. > >> c:\cygwin\bin\echo.exe %PATH%-- works fine > >> c:\cygwin\bin\echo.exe %PATH%%PATH% -- fails, immediately returns to > com

RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

> Igor wrote: > You may be hitting the command-line limit with bash. Try the above with > cmd.exe. See below. >> c:\cygwin\bin\echo.exe %PATH%-- works fine >> c:\cygwin\bin\echo.exe %PATH%%PATH% -- fails, immediately returns to command line > >Try stracing the last line above... >

RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

On Wed, 12 Mar 2003, Willis, Matthew wrote: > Igor wrote: > > >Matt, > > > >A virus checker *shouldn't* affect your command line length limit... > >Try running the offending command under strace, e.g., > > > >strace -o echo.strace /usr/bin/echo ${PATH}${PATH} > > > >and look at the tail of the out

RE: cygwin 1.3.20-1 - strange problems with long command lines in nt4

Igor wrote: >Matt, > >A virus checker *shouldn't* affect your command line length limit... >Try running the offending command under strace, e.g., > >strace -o echo.strace /usr/bin/echo ${PATH}${PATH} > >and look at the tail of the output. That should give you a clue of where >it's hanging. If y

Re: cygwin 1.3.20-1 - strange problems with long command lines in nt4

On Tue, 11 Mar 2003, Willis, Matthew wrote: > I've had the same problem for a couple of months (since 1.3.13 anyway); > certain long command lines just fail to work for me. I've updated to the > most recent (1.30.20-1 as of march 11) and I find the problem just got worse > for me. > > If I cd to a

cygwin 1.3.20-1 - strange problems with long command lines in nt4

I've had the same problem for a couple of months (since 1.3.13 anyway); certain long command lines just fail to work for me. I've updated to the most recent (1.30.20-1 as of march 11) and I find the problem just got worse for me. If I cd to a directory with many files, I issue "ls *" and the termi