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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Andrew Markebo Subject: Re: ls : fails with a long list Date: Wed, 12 Mar 2003 22:59:22 +0100 Lines: 21 Message-ID: References: <000901c2e8d6$ee2bf9e0$c29ac250 AT leper> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2 Cancel-Lock: sha1:LHjpO/R5jEb2JJ3vZxY/1szsGiU= / wrote: |>> Got two words for you: 'find' and 'xargs'... ;-) | | Thank you. I guess I phrased myself badly. I wasn't saying "How do I do | this?" (I think ls -AlR gives me pretty well what I was after). I was saying | "Once I could do this. Now I can't. Does anybody know if anything has | altered recently? and can anybody explain the phenomenon?" Anyway, it seems | from an earlier response to be something bash-related, so I imagine for the | moment I am stuck with it. Thanks again. Fergus Well it is related to the shell yes. Limitation of the length of the prompt the shell can handle. (I think ;-)) More and more files coming into the subdir, or the contents are static? Or hmm, could be a compilation switch to the compilation of bash, but wouldn't think so.. /Andy -- The eye of the beholder rests on the beauty! -- 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/