You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some options in readline [1] make lnav misbehave. Note that this happens in Zsh as well even though it doesn't use readline.
All examples are in inputrc
This crashes lnav after pressing ;
set editing-mode vi
set show-mode-in-prompt on
This shows the behavior below
set editing-mode vi
set show-mode-in-prompt on
set vi-ins-mode-string \1\e[6 q\2
set vi-cmd-mode-string \1\e[2 q\2
I press :123456789123456789 nothing appears in the command bar until 23456789, so :1234567891 aren't visible (same thing if I start with ;). I press <escape> and what I see 232 q:123456789123456789. If I press <enter> I get ✘ error: unknown command - 123456789123456789 which is to be expected, but command bar don't seem to behave properly.
Thank you for the clarification. I have bindings for effective editing & navigation based on Emacs readline [1], and disabling show-mode-in-prompt solves the issue. If readline support is removed, I hope the replaced solution is able to replicate this workflow.
lnav version: 0.12.2
Some options in readline [1] make
lnav
misbehave. Note that this happens in Zsh as well even though it doesn't use readline.All examples are in
inputrc
;
I press
:123456789123456789
nothing appears in the command bar until23456789
, so:1234567891
aren't visible (same thing if I start with;
). I press<escape>
and what I see232 q:123456789123456789
. If I press<enter>
I get✘ error: unknown command - 123456789123456789
which is to be expected, but command bar don't seem to behave properly.[1] https://wiki.archlinux.org/title/Readline
The text was updated successfully, but these errors were encountered: