CursorMovedC triggered at wrong pos when using setcmdpos() #15064
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zeertzjq
force-pushed
the
cmdlinemovedc
branch
3 times, most recently
from
764f05a
to
397ce9f
Compare
Problem: CursorMovedC triggered at wrong pos when using setcmdpos().
Solution: Remove the premature triggering. Also don't trigger when
cursor didn't move.
|
thanks! |
zeertzjq
added a commit
to zeertzjq/neovim
that referenced
this pull request
Jun 21, 2024
Problem: CursorMovedC triggered wrongly with setcmdpos()
(after v9.1.0507)
Solution: Remove the premature triggering. Also don't trigger when
cursor didn't move. (zeertzjq)
closes: vim/vim#15064
vim/vim@bc6f967
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem: CursorMovedC triggered at wrong pos when using setcmdpos().
Solution: Remove the premature triggering. Also don't trigger when
cursor didn't move.