set -o vi did the job. Behavior is now exactly like in ksh. Thanks. Rudy On Thu, Apr 03, 2003 at 03:09:18PM -0700, L. C. Robinson wrote: > You can set vi editing mode in bash, something like > set -o vi > But I'd have to look it up to be sure. > > But if you are used to ksh, why switch? Just make sure > the pdksh package is installed, and change your shell > via the chsh utility. You might have to make sure > ksh is listed in /etc/shells, if the package installer > doesn't do it for you, for chsh to allow that shell. > > I used to be a ksh user, till I discovered zsh, which > is a great superset of ksh and all the other shells; > you might want to take a look at that, too. > > LCR > > On Thu, 3 Apr 2003, A. R. Vener wrote: > > > I am a ksh user. > > > > In ksh I can press the escape key and select > > a previous command line to edit and execute using the +, - and v keys. > > > > I now have to access a system that only has bash and > > this procedure doesn't work in bash. Can someone familiar > > with the bash version of command line editing help me out here? > > > > My FCEDIT environmental variable is defined as vi if > > that makes any odds. > > -- > L. C. Robinson > reply to no_spam+munged_lcr@xxxxxxxxxxxxxxxxxxx > > People buy MicroShaft for compatibility, but get incompatibility and > instability instead. This is award winning "innovation". Find > out how MS holds your data hostage with "The *Lens*"; see > "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html > > > > _______________________________________________ > > Blinux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/blinux-list _______________________________________________ Blinux-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/blinux-list