octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54672] Unexpected behavior on first input, du


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #54672] Unexpected behavior on first input, due to ~/.inputrc
Date: Tue, 18 Sep 2018 12:03:55 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36

Update of bug #54672 (project octave):

                Category:             Interpreter => Documentation          
                Severity:              3 - Normal => 2 - Minor              
                Priority:              5 - Normal => 3 - Low                
              Item Group:              Regression => Documentation          
                  Status:            Works For Me => Need Info              
                 Summary: Odd behavior on first input => Unexpected behavior
on first input, due to ~/.inputrc

    _______________________________________________________

Follow-up Comment #10:

Yes, it is a good idea to allow the user's ~/.inputrc to override Octave's
default inputrc. I have been doing that in my own ~/.octaverc for years. And
bug #49323 was about the opposite undesirable behavior, that Octave's inputrc
was overriding only portions of the user's preferred ~/.inputrc. Octave is now
doing the correct thing, loadings its own default settings first, and then
loading the user's preferred readline configuration.

We can leave this bug open to discuss where and how this should be documented
better.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]