Re: bash vs csh

[Cesar Moya <cesar1907 yahoo com>]

Hey guys:

Thank you very much for all your answers.  I tried what you
all suggested and seems to be working.  Of course I put
kedit as an example in my original post, but I was worried
about my own C or FORTRAN programs which sometimes I leave
running in the background and need to be sure they are not
killed by just closing the console from where I started 
them.

BTW, how do I get "gvim"? I heard about it, but never tried
it.

And one? more thing on this issue of shells.  I wanted to
add color to "ls" command and found that all I needed was
to put the "etc/DIR_COLORS" as " /home/cesar/.dir_colors"
for example, edit to my liking, and then add

alias ls='ls --color=tty'

This works fine for the bash shell, just changing color to
whatever I like in my .dir_colors, but cannot make it work
in the csh shell.  The csh shell always takes the default
in "etc/DIR_COLORS".

Cesar




--- Gordon Messmer <yinyang eburg com> wrote:
> On Wed, 2002-05-01 at 07:58, Brian Ashe wrote:
> > 
> > At least in KDE you can save yourself from worrying
> about this at all. Hit
> > Alt-F2 and you get a run dialog. Type your command in
> and hit enter. It has
> > to be one of the handiest things about KDE. (Note: If
> Gnome has a similar
> > feature I am not aware of it.) It also has a history of
> commands you've
> > entered, so you can just use a pulldown for previous
> commands.
> 
> Not only is is present in GNOME, it uses the same default
> keybinding  :)
> 
> 
> 
> 
> _______________________________________________
> Redhat-list mailing list
> Redhat-list redhat com
> https://listman.redhat.com/mailman/listinfo/redhat-list


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com