http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c1 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement --- Comment #1 from Dr. Werner Fink --- Debian does not have by default a /etc/inputrc but only a short /usr/share/readline/inputrc and AFAIK the history-search-backward feature is disabled by default. I simply do set -o vi and press ESC then I do CursorUp and CursorDown and nver tried PgUp/PgDn as I prefere emacs mode. And the lines in my "/etc/inputrc" "\e[5~": history-search-backward "\e[6~": history-search-forward are outside of any mode setting ... if you have a working inputrc with the two lines for vi editing mode then show me the WorksOnDebian[tm] solution. That is how to avoid that the ~ in "\e[5~" or "\e[6~" seesm to be splitted in vi mode -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek@suse.com Flags| |needinfo?(msuchanek@suse.co | |m) --- Comment #3 from Dr. Werner Fink --- I'm going to close this as INVALID as the settings in /etc/inputrc become reset by the line set -o vi and this requires two lines bind -m vi-insert -f /etc/inputrc bind -m vi-command -f /etc/inputrc for both the VI command and insert editing mode ... OK I could set set editing-mode vi as default but I will not do this as VI editing is not common and any user which wants to use the VI editing mode should do a copy of /etc/inputrc to ~/.inputrc and add the line set editing-mode vi at the very beginning. nevertheless I'd like to know what WorksOnDebian[tm] means as this requires a hacked readline linrary or a complicated solution within the bash profile/init files -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c5 --- Comment #5 from Michal Suchanek --- WorksOnDebian(tm) means that whether you set -o emacs or set -o vi the settings in /etc/inputrc just work. I just use the library. I do not want to know how it accomplishes this internally. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c7 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msuchanek@suse.co | |m) | --- Comment #7 from Michal Suchanek --- + . test-bind.sh ++ set -o ++ grep -E '^(emacs|vi)' emacs off vi on ++ grep history-search ++ bind -P history-search-backward can be found on "\e[5~". history-search-forward can be found on "\e[6~". ++ grep history-search ++ bind -m vi-insert -P history-search-backward can be found on "\e[5~". history-search-forward can be found on "\e[6~". ++ grep history-search ++ bind -m vi-command -P history-search-backward is not bound to any keys history-search-forward is not bound to any keys -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c9 --- Comment #9 from Dr. Werner Fink --- (In reply to Michal Suchanek from comment #7)

+ . test-bind.sh ++ set -o ++ grep -E '^(emacs|vi)' emacs off vi on ++ grep history-search ++ bind -P history-search-backward can be found on "\e[5~". history-search-forward can be found on "\e[6~". ++ grep history-search ++ bind -m vi-insert -P history-search-backward can be found on "\e[5~". history-search-forward can be found on "\e[6~". ++ grep history-search ++ bind -m vi-command -P history-search-backward is not bound to any keys history-search-forward is not bound to any keys

Attach the /etc/inputrc as well as the ~/.inputrc from this Debian system. Then I can test this on a openSUSE version of libreadline -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c11 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #11 from Dr. Werner Fink --- (In reply to Michal Suchanek from comment #10)

Created attachment 722550 [details] /etc/inputrc

No ~/.inputrc

And again, I am not requesting that the vi mode is made the default. I am merely requesting that the vi mode is fixed so the bindings apply in it as well.

Obviously the conditional in the SUSE /etc/inputrc is supposed to do that but is broken.

Obviously? Do you have tried to use the Debian /etc/inputrc as personal ~/.inputrc and used export INPUTRC=~/.inputrc bash with this I see werner@boole:~> echo $INPUTRC /suse/werner/Downloads/inputrc.debian werner@boole:~> set -o vi werner@boole:~> bind -P | grep history-search history-search-backward is not bound to any keys history-search-forward is not bound to any keys werner@boole:~> bind -m vi-command -P | grep history-search history-search-backward is not bound to any keys history-search-forward is not bound to any keys werner@boole:~> bind -m vi-insert -P | grep history-search history-search-backward is not bound to any keys history-search-forward is not bound to any keys werner@boole:~> binD no history-search-backward on PageUp ... I'll do a real fix for Tumbleweed but not for Leap nor SLES12 as this is a bit touchy -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c13 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Dr. Werner Fink --- Fixed for one of the next Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c15 --- Comment #15 from Michal Suchanek --- Actually, it does not work for me at all with the new bash even with /etc/inputrc and /etc/inputrc.keys from latest aaa_base and in emacs mode. All I get is a tilde. How is this intended to work? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1035785 http://bugzilla.suse.com/show_bug.cgi?id=1035785#c17 --- Comment #17 from Dr. Werner Fink --- Just tested within an autobuild environment with latest aaa_base + latest bash (4.4.12) + latest libreadline7 and it works flawless in emacs as well as in both vi modes -- You are receiving this mail because: You are on the CC list for the bug.