[plug] Anyone got bash tips for an old korn shell user?
Alan Graham
alan.graham at infonetsystems.com.au
Wed Sep 4 20:59:15 WST 2002
Unbelievable. I do a 'set -o vi' all the time under ksh, as a lot of
clients have it set to emacs. I just never thought of trying this on
bash (*hangs head in shame*).
Oh and thanks Colin as well, but this vi style searching and editing was
what I was after. After all, we all know that vi is the editor of
choice for the cognoscenti, don't we?
;-)
Thanks guys
On Wed, 2002-09-04 at 20:43, Mark Haselden wrote:
> On Wed, Sep 04, 2002 at 08:11:46PM +0800, Alan Graham wrote:
> > The majority of my commercial *nix experience has been on AIX, which
> > used to use ksh as the default shell. No problems there, I find it for
> > easier to use than csh, with vi as my editor.
> >
> > All versions of linux set up bash as the shell. I install pdksh
> > everywhere I can, which keeps me happy, but I still keep having to use
> > bash on other accounts.
> >
> > The main problem I have is history. If I want to find an old command in
> > the history with ksh, I just <esc>, /search string, and <n> back through
> > all occurrences. I can even edit it.
> >
>
> Try typing "set -o vi" at the bash prompt. That should give bash
> the behaviour that you want, if I've understood you correctly..
>
> set -o emacs to reverse the mode back to normal
>
> Cheers
>
> Mark
>
>
> --
> Being a Unix system administrator is like being a tech in a biological
> warfare laboratory, except that none of the substances are labeled
> consistently, any of the compounds are just as likely to kill you by
> themselves as they are when mixed with one another, and it is never
> clear what distinction is made between a catastrophic failure in the lab
> and a successful test in the field.
>
> Michael Tiemann
>
More information about the plug
mailing list