bugGNU Octave - Bugs: bug #34920, Unable to access command history

 
 

bug #34920: Unable to access command history

Submitter:  None
Submitted:  Mon 28 Nov 2011 04:35:07 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Joanna Cheng Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 3.2.4
Operating System:  * Microsoft Windows Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Thu 09 Jan 2014 12:05:55 PM UTC, comment #7: 

Eigil, is bug #41124 your problem?

Jordi Gutiérrez Hermoso <jordigh>
Group Member
Thu 09 Jan 2014 06:22:11 AM UTC, comment #6: 

On my mac in the gui in Octave 3.8. I can't access the history at all w. C-p, C-n or the arrow keys.

I'm using the binaries from octave forge.



Eigil Krogh <ekrogh>
Mon 27 Feb 2012 01:26:49 PM UTC, comment #5: 

Sure, I'm closing it.

Jordi Gutiérrez Hermoso <jordigh>
Group Member
Mon 27 Feb 2012 06:00:01 AM UTC, comment #4: 

Can this bug be closed?  The issue is with Readline, not Octave.  Furthermore, it doesn't seem to be a bug that a certain key combination enters vi mode.

Rik <rik5>
Group administrator
Mon 28 Nov 2011 10:49:46 PM UTC, comment #3: 

jwe: You're right, that's what it has done. Seems to be an incomplete implementation of vi editing mode though.
I was actually looking for this option after Jordi told me it existed; I inadvertently found it (and didn't even realise) :)

> You can see the keybindings with C-x k.

This doesn't work for me. Tried all the various combinations (C-x k, C-x C-k, ESC C-x k, ESC C-x C-k, etc). I'm expecting some kind of output, right? A list of keybindings?

Anonymous
Mon 28 Nov 2011 07:42:59 AM UTC, comment #2: 

Is it possible that you entered readline's vi editing mode?  By default, that is bound to ESC C-j and ESC C-m.  You can see the keybindings with C-x k.  Unfortunately, the emacs-editing-mode command is not bound to a key by default, so I don't know how to exit the vi mode and return to emacs mode unless you add a key binding for the readline emacs-editing-mode function in your ~/.inputrc file.

John W. Eaton <jwe>
Group administrator
Mon 28 Nov 2011 04:36:52 AM UTC, comment #1: 

I've had this happen too, very rarely, on Debian. It's like readline completely dies. I don't know what causes it either.

Jordi Gutiérrez Hermoso <jordigh>
Group Member
Mon 28 Nov 2011 04:35:07 AM UTC, original submission:  

Occasionally (unable to pinpoint exact circumstances), I stop being able to access my command history.

Neither the arrow keys nor readline commands work. Readline commands just give ^A, ^E, ^P, ^N etc input on screen. Arrow keys give no output.

e.g.

octave-3.2.4.exe:39> ^P^N^A^E
error: invalid character `►' (ASCII 16) near line 39, column 2
parse error:

>>> ►♫☺♣

^G then <enter> in this situation gives me a system bel as expected; this does NOT work when on a working (i.e. arrow keys/readline commands working) window.

This only seems to happen on one install, on XP SP3. I have a similar install (same version of Octave) on a Vista and a Win7 install. Don't have another XP install to test on.

Octave was installed using the binary installer here: http://s3.amazonaws.com/mlclass-resources/software/Octave-3.2.4_i686-pc-mingw32_gcc-4.4.0_setup.exe

Anonymous

 

(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 ekrogh (Posted a comment)
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by jordigh (Posted a comment)
  • -email is unavailable- added by None (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
    2014-01-09 jordigh CategoryInterpreter GUI
        Item GroupPerformance Incorrect Result
    2012-02-27 jordigh StatusNone Invalid / Not an Octave Bug
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code