From owner-freebsd-questions Wed Mar 22 19:52:21 2000 Delivered-To: freebsd-questions@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 45DD937C031 for ; Wed, 22 Mar 2000 19:52:17 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id TAA85804; Wed, 22 Mar 2000 19:51:54 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38D994DA.D49429A4@gorean.org> Date: Wed, 22 Mar 2000 19:51:54 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-HEAD-0320 i386) X-Accept-Language: en MIME-Version: 1.0 To: rene@tp98.catv.szabinet.hu Cc: R Joseph Wright , Matthew Jonkman , freebsd-questions@FreeBSD.ORG Subject: Re: Shell Color Coding References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rene Scott wrote: > Maybe a better approach to define a function like > > function ls > { > gnuls --color=auto $@ > } > > And with 'alias ls='gnuls --color=always' the following shell code on > the command line should fail: > > for i in `ls`; do > ... > done A) Why should it fail? B) It doesn't. :) C) A better approach for your command line script is: for i in *; do Good luck, Doug -- "So, the cows were part of a dream that dreamed itself into existence, is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message