[Top][All Lists]

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

[Octave-bug-tracker] [bug #49323] Readline library does not support vi-m

From: Rik
Subject: [Octave-bug-tracker] [bug #49323] Readline library does not support vi-mode correctly
Date: Thu, 13 Oct 2016 02:01:11 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0

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

For what it's worth, my version of readline is 6.3-8ubuntu1.  I only see the
issue when the editing-mode is set to vi.  Maybe this is some sort of memory
corruption?  It is very odd because even the right arrow key causes a

Test ~/.inputrc file

set editing-mode vi
set keymap vi-command
"\C-f": dump-functions
"\C-g": dump-macros
set keymap vi-insert
"\e[D": "Hello"
"\C-f": dump-functions
"\C-g": dump-macros
set show-mode-in-prompt on
set keyseq-timeout 250

Thes maps the left arrow to produce the text "Hello".

octave-cli -f -q
12<Left Arrow>   # This will correctly insert "Hello" after 12
graphics_toolkit fltk
123<Left Arrow>  # '3' is deleted, cursor moves to 2, mode changes to command
# Change .inputrc to map Left Arrow to "bye"
readline_read_init_file ("~/.inputrc")
\e[D outputs bye
123<Left Arrow>  # '3' is deleted, cursor moves to 2, mode changes to command

>From the last test, I can see that Readline knows what it should be
generating, but it isn't doing it.  Is it possible that the terminal is now
producing a different escape sequence for the left arrow that doesn't match


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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