[Octave-bug-tracker] [bug #54672] Unexpected behavior on first input, due to ~/.inputrc

[Mike Miller]

Follow-up Comment #20, bug #54672 (project octave):

Oh, I see. I think your interpretation of the configuration is not correct.
The configuration was not wrong or conflicting with Octave in some way. I
assumed that when you discovered it was the cause, that you knew how vi mode
works with readline.

The configuration file 'set keymap vi' was putting your input into vi command
mode instead of insert mode. If you are familiar with vi, this means that any
keys you input are commands instead of sent to the input buffer. When you
pressed the 'c' key, readline went into replace-and-insert mode. If you had
typed the 'a' key it would have gone into append mode. But the 'e' key, for
example, only advances the cursor, so it would have seemed to be doing
nothing. The 'j' and 'k' keys scroll through the command history.

This is an entirely valid configuration to be in with respect to how readline
works and doesn't have anything to do with Octave in particular at all.

When I start a Python interactive shell with the same .inputrc, I get the
exact same behavior, it starts in vi command mode.

Does this help explain why there is not really anything wrong with this
configuration, and therefore why I think there is nothing for Octave to detect
or warn about?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?54672>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/