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
> > 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 unalias
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 lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Williams, Gerald S (Jerry) on 11/23/2005 7:18 AM:
> Alireza Ghasemi wrote:
>
>>I have the same problem about ls too. Do they
>>ever support syntax highlighting ?
>
>
> For ls, this might work for you:
>
> alias ls='ls -color=auto '
Alireza Ghasemi wrote:
> I have the same problem about ls too. Do they
> ever support syntax highlighting ?
For ls, this might work for you:
alias ls='ls -color=auto '
-gsw
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.ht
Goto /usr/share/vim/vim64 and copy the file
vimrc_example.vim to /usr/share/vim/vimrc.
Jurgen
"Alireza Ghasemi" <[EMAIL PROTECTED]>
Sent by:
[EMAIL PROTECTED]
2005-11-23 11:52 AM
To
cc
Subject
syntax highlighting in vim
Classification
Hello,
I have instal
Hello,
I have installed almost whole cygwin from an ISO snapshot. When using vim in
it I realized that it doesn't highlight .c or .cc files. " :syntax enable "
didn't work.Can anybody help me about it ? I have the same problem about ls
too.Do they ever support syntax highlighting ?
--
Unsubscrib
7 matches
Mail list logo
