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

[Mike Miller]

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

I agree that I am not the right person or example audience to figure out how
this should be documented (including the possibility of a warning message).

I would recommend avoiding the word "unpredictable", because everything you
experienced is entirely predictable and well behaved, maybe not obvious or
clearly described.

In order to remove myself from the decision process, I would recommend
comparing the behavior of Octave with other programs that also use readline
and are affected by the user's ~/.inputrc or lack thereof. I have already
tested Python and verified that it behaves the same as Octave when I run a
Python interactive shell, and no warning message is printed about the
existence of ~/.inputrc. How does GNU bc behave? How about gdb, guile, or
units? I guess that most or all of them silently load ~/.inputrc.

    _______________________________________________________

Reply to this item at:

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

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