X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Subject:	RE: syntax highlighting in vim
Date:	Wed, 23 Nov 2005 09:51:48 -0500
Message-ID:	<94BF3137C62D3E4CAED7E97F876585F0D037CE@pauex2ku08.agere.com>
From:	"Williams, Gerald S \(Jerry\)" <gsw AT agere DOT com>
To:	<cygwin AT cygwin DOT com>
Cc:	"Alireza Ghasemi" <fooladgh AT gmail DOT com>, "Eric Blake" <ebb9 AT byu DOT net>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id jANEq8A9018444

Eric Blake wrote:
> Actually, a better spelling would be
> alias ls='ls --color=auto'

Oops, I should have used cut and paste rather than
typing it. I meant this of course:

  alias ls='ls --color=auto '

> The use of a trailing space in the alias controls
> whether the next word on the command line will also
> be subject to alias expansion;

True, but I prefer not to make assumptions about how
people are using aliases. The space at the end of the
alias makes it behave like the unaliased ls in that
regard.

-gsw


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -