This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: long command lines

To: cygwin at cygwin dot com
Subject: Re: long command lines
From: Christopher Faylor <cgf at redhat dot com>
Date: Mon, 29 Jan 2001 16:59:42 -0500
References: <3A70B734.A18289E@nuance.com> <3A70C7CB.AB0DA2BE@yahoo.com> <4.3.1.2.20010129110023.022b0468@pop.ma.ultranet.com> <3A75E410.1E5421C3@digitalfocus.com>
Reply-To: cygwin at cygwin dot com

On Mon, Jan 29, 2001 at 04:43:44PM -0500, Daniel Barclay wrote:
>"Larry Hall (RFK Partners, Inc)" wrote:
>> 
>> At 10:52 AM 1/29/2001, Daniel Barclay wrote:
>> >...
>> >I thought GNU software tried to avoid arbitrary limit like that.  Shouldn't
>> >the only limit be virtual memory?
>> >
>> >That is, shouldn't bash keep reallocating (enlarging) its buffer until the
>> >pattern has been expanding, or until it runs out of memory?
>> 
>> I'm sure you can find your answer in the source if you're interested.
>
>What's up with your attitude?

What, specifically, are you objecting to?  The suggestion that you could
figure this out for yourself by looking at the sources?

Or were you assuming that Larry knew the answer and was selfishly withholding
information?

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Follow-Ups:
- Re: long command lines (off topic by now)
  - From: Daniel Barclay

References:
- long command lines
  - From: Mike Schuster
- Re: long command lines
  - From: Earnie Boyd
- Re: long command lines
  - From: Larry Hall (RFK Partners, Inc)
- Re: long command lines
  - From: Daniel Barclay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]