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
(Examples with evil-escape-key-sequence set to "fd")
In ansi-term and other term-buffers, when running less, if the user
presses f, the file being viewed is actually scrolled down twice
instead of once as it should be.
This is because evil-escape causes an f key press from the user to
be sent as the following sequence of key presses:
f <backspace> f
In general, term-mode can be running some arbitrary program that
doesn't interpret f <backspace> f as equivalent to f. In that
case, it doesn't seem like evil-escape is completely safe to use in
term-mode at all, since it's sending key sequences to an arbitrary
terminal program that don't correspond to the user's intention.
Perhaps evil-escape-excluded-major-modes should include term-mode
by default, as evil-escape's support for it works sometimes but is
not correct in all cases.
The text was updated successfully, but these errors were encountered:
bcc32
added a commit
to bcc32/dotfiles
that referenced
this issue
Jan 17, 2024
(Examples with
evil-escape-key-sequence
set to"fd"
)In ansi-term and other term-buffers, when running
less
, if the userpresses
f
, the file being viewed is actually scrolled down twiceinstead of once as it should be.
This is because
evil-escape
causes anf
key press from the user tobe sent as the following sequence of key presses:
In general, term-mode can be running some arbitrary program that
doesn't interpret
f <backspace> f
as equivalent tof
. In thatcase, it doesn't seem like evil-escape is completely safe to use in
term-mode at all, since it's sending key sequences to an arbitrary
terminal program that don't correspond to the user's intention.
Perhaps
evil-escape-excluded-major-modes
should includeterm-mode
by default, as evil-escape's support for it works sometimes but is
not correct in all cases.
The text was updated successfully, but these errors were encountered: