X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: syntax highlighting in vim Date: Wed, 23 Nov 2005 13:13:13 -0500 Message-ID: <94BF3137C62D3E4CAED7E97F876585F0D037E5@pauex2ku08.agere.com> From: "Williams, Gerald S \(Jerry\)" To: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id jANIDYkN015562 Eric Blake wrote: > Wrong again - alias expansion in bash starts ONLY at the > first word, and only progresses on to the next word if > the current alias expansion ended in a space. I stand corrected. In the first job where I used ksh, they had set up aliases for everything with the spaces at the end (including ls and cd) and added "convenient" aliases for some parameters. Even though I've long since abandoned the use of aliases for parameters, I've been keeping the spaces at the end of my aliases thinking it was more flexible. That's it. I'm ditching the spaces. 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/