[Octave-bug-tracker] [bug #54672] Odd behavior on first input

[Michael Godfrey]

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

Well, after all this was easy with the help of
Dmitri and Mike. I had recently
changed my .inputrc file from empty to handle some
input differently.  My .inputrc was changed from empty to:

set keymap vi

Deleting that line fixed the problem. One
way to deal with this would be to test for an incompatible
.inputrc file. However, is it really a good idea to
allow the user's .inputrc file to replace Octave's?
At least some user's would prefer Octave's default while
in Octave, but use their own otherwise.

Also, the description in the Manual (pg.32) is not clear.
It states:  The default configuration file is
normally ~/.inputrc.

But, it does not describe what happens if .inputrc is empty.

An obvious choice would be another command line argument to
allow choice of use octaverc or use .inputrc. It seems to me
that the default should be to only use the Octave
configuration.  This would have avoided my problem...
And, it would mean that most users (those who do not explicitly
choose otherwise) would have the environment settings.

Now the only reason to keep this report open would be a discussion of any
change to octaverc. At least the 
consequences of running Octave with a non-empty
~/.inputrc should be documented.

Thanks again Dmitri and Mike


    _______________________________________________________

Reply to this item at:

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

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