bugGNU Octave - Bugs: bug #46352, Command prompt does not...

 
 

bug #46352: Command prompt does not autocomplete last command beginning with a string

Submitter:  Francisco Vico <nightcod3r>
Submitted:  Sun 01 Nov 2015 09:01:01 AM UTC
   
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  nightcod3r Open/Closed:  * Closed
Release:  * 3.8.1 Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 01 Nov 2015 07:10:06 PM UTC, comment #3: 

The `-f` option skips loading all initialization files, including the default readline initialization file (/usr/share/octave/$VERSION/m/startup/inputrc). So what you are seeing is the expected behavior with the `-f` option.

Mike Miller <mtmiller>
Group Member
Sun 01 Nov 2015 06:44:53 PM UTC, comment #2: 

Thanks for prompt reply. You're right, Mike, there's a difference in how both sessions did start. `octave -qf` does not show the auto-complete behavior, while `octave` does. But I fail to understand, since there's nothing in the ~/.octaverc file, so it does not affect the initialization.

Francisco Vico <nightcod3r>
Sun 01 Nov 2015 03:19:29 PM UTC, comment #1: 

Hi, thanks for your bug report. This behavior works for me by default. Can you tell what is different between the two sessions of Octave that show different behavior? What options are you using to start Octave? Do you have a ~/.octaverc?

The relevant readline bindings are the following:


"\e[A": history-search-backward
"\e[B": history-search-forward


If you load the system /etc/inputrc or ~/.inputrc and use a different binding for the up and down arrow keys, you will get different behavior.

Mike Miller <mtmiller>
Group Member
Sun 01 Nov 2015 09:01:01 AM UTC, original submission:  

I used to recover in Octave the last command beginning with a certain string by typing it and then pressing the up arrow key. Sometimes this behavior does not reproduce in the command line. Meaning, I type something, press up, and the very last command shows up, no matter if a previous one starting with that string is in the stack.

The behavior looks weird. I've been running the 3.8.1 release in two different tabs of the same Ubuntu terminal, one displaying the good-old behavior, the other not.

Francisco Vico <nightcod3r>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by nightcod3r (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2015-11-01 mtmiller StatusNeed Info Invalid / Not an Octave Bug
        Open/ClosedOpen Closed
    2015-11-01 mtmiller CategoryNone Interpreter
        StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code