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 Message-ID: <3A70D238.3B4CBB5D@jpl.nasa.gov> Date: Thu, 25 Jan 2001 17:26:16 -0800 From: Jon Ericson Reply-To: Jonathan.L.Ericson@jpl.nasa.gov X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Schuster CC: cygwin@cygwin.com Subject: Re: long command lines References: <3A70B734.A18289E@nuance.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mike Schuster wrote: > > Problem: I couldn't figure out how to get very long command line > arguments to work (~32k) (for example 'ls */*/*/*', if you have a lot of > files on the disk). > > Question: Does anybody know if this > a) a Windows problem, > b) a cygwin problem, > c) something that can easily be fixed by setting some parameter > (Which?). You should be using some combination of find and/or xargs rather than wildcard expansion. For instance, "find .". This is a general shell issue not limited to either Windows or cygwin. Jon -- Knowledge is that which remains when what is learned is forgotten. - Mr. King -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple