Click to See Complete Forum and Search --> : command line editing hosed?


HairyCane
03-09-2001, 02:47 PM
I would think this is a simple bash thing, but I can't get it to work. 2 problems:

1. I'm a vi guy :p . If I do set -o vi, I can't use ESC-k to go to last command. If I do set -o emacs, ctrl-P works...set -o says vi is on, emacs off...

2. file completion via ESC-ESC stopped working, no clue why.

bigrigdriver
03-09-2001, 09:35 PM
Your first problem sounds like some kind of conflict between vi an emacs, trying to use the same memory block, or some such. You may be limited to using one or the other, but not both at once.
The second problem is more straightforward. I use vim (the updated vi). The command sequence is "ESC" (to quit insert mode), then ":wq" to write changes and quit. :cool:

HairyCane
03-10-2001, 11:46 AM
Bash takes care of the conflict. It's only set for emacs or vi, not both at the same time. I should have been clearer on one statement. When the set shows editor set to vi, it is after set -o vi. When I do set -o emacs, set says emacs.

The file completion problem is on the command line, not in the editor.