New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:terminal output completes pending op (d, y, ...) #5398
Labels
Milestone
Comments
Alternative reproduction steps in #5417. |
fwalch
added
bug
issues reporting wrong behavior
terminal
built-in :terminal or :shell
labels
Oct 3, 2016
Possibly the same root cause as #6166. |
justinmk
changed the title
High volume terminal output makes
:terminal output completes pending op (d, y, ...) #
Mar 10, 2017
d
not wait for an argument
justinmk
changed the title
:terminal output completes pending op (d, y, ...) #
:terminal output completes pending op (d, y, ...)
Mar 10, 2017
hardenedapple
added a commit
to hardenedapple/neovim
that referenced
this issue
Sep 2, 2017
hardenedapple
added a commit
to hardenedapple/neovim
that referenced
this issue
Sep 2, 2017
hardenedapple
added a commit
to hardenedapple/neovim
that referenced
this issue
Sep 2, 2017
hardenedapple
added a commit
to hardenedapple/neovim
that referenced
this issue
Sep 3, 2017
nateozem
pushed a commit
to nateozem/neovim
that referenced
this issue
Oct 5, 2017
normal_finish_command() and normal_prepare() assume that any pending operator needs to be finished after any subsequent key. Set `finish_op = false` in nv_event() to indicate that the pending operator shouldn't be finished in normal_execute(). This is how nv_visual() indicates that 'v' or 'V' in operator-pending mode should not finish the current pending operator. fixes neovim#5398 fixes neovim#6166 (partially; mappings are still interrupted)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I started using neovim last week, and one of my favorite features is the built-in terminal. It's extremely convenient. I'm coming from Emacs + Evil, and one of my longtime gripes was that eterm is terrible. Somehow neovim's terminal is exactly right, except for a few minor issues. In this case, if I have a big terminal window, output in the terminal can screw up input into text buffers.
$TERM
: xterm-256colorActual behaviour
When a program prints lots of things in TERMINAL mode, typing
d
in text buffers immediately deletes a line, as though you had typeddd
. With really high volume output, other weird things seem to happen, but they're harder to reproduce without spamming so hard that my computer freezes.Expected behaviour
d
should wait for a text object as an argument, as it does in normal situations.Steps to reproduce using
nvim -u NORC
The text was updated successfully, but these errors were encountered: