On 1/21/18 12:23 PM, gaze...@xmission.com wrote:
> 3) Using Escape v to edit a command line in vi mode works, but leaves the
> keyboard in a funny state. Specifically, it leaves you at the next bash
> prompt, but
> in "vi mode" - i.e, hitting k displays the previous line in the history
> rather than
> entering a 'k'. The user effect is that the keyboard appears to be "stuck"
> until you
> hit ^C to reset things.
It just doesn't change the editing mode. If you were in command mode and
used `v' to edit and execute the command, you're still in command mode when
the edited file completes. You don't have to ^C; you can just use `i' to
enter insert mode like usual.
The Posix description of this editing command doesn't explicitly state that
the command leaves you in insert mode, but I agree that it probably makes
more sense to force readline into insert mode at this point. I'll look at
that.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
