Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 25 Jan 2001 23:58:14 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: long command lines Message-ID: <20010125235814.B12186@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3A70B734.A18289E@nuance.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from dkarr@tcsi.com on Thu, Jan 25, 2001 at 04:42:03PM -0800 On Thu, Jan 25, 2001 at 04:42:03PM -0800, David M. Karr wrote: >>>>>> "Mike" == Mike Schuster writes: > Mike> Problem: I couldn't figure out how to get very long command line > Mike> arguments to work (~32k) (for example 'ls */*/*/*', if you have a lot of > Mike> files on the disk). > > Mike> Question: Does anybody know if this > Mike> a) a Windows problem, > Mike> b) a cygwin problem, > Mike> c) something that can easily be fixed by setting some parameter > Mike> (Which?). > >Before, when I only worked on Unix (with Ksh, NOT Csh), I used to use >command lines like this all the time: > > somecmd $(find . -type f) > >When I started needing to do similar things on Cygwin, I discovered >the line length problem, and concluded there was no "fix" for it. I assume that you concluded this from an exhaustive study of the source code. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple