-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
This extension breaks the Add Next Occurrence
command and shortcut
#1311
Labels
Comments
RodrigoRoaRodriguez
changed the title
Bug: This extension breaks the
This extension breaks the Feb 22, 2017
Add Next Occurrence
command and shortcutAdd Next Occurrence
command and shortcut
Update:
The second issue described(the Add Next Occurrence command) has been fixed but the first one (the shortcut being ignored) still applies. |
Update:
This issue still applies for insert mode but does no longer seem to apply for normal mode. |
Ctrl-d only works in visual mode for me |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The VSCodeVim team prioritizes issues based on reaction count.
Add Next Occurrence
shortcut is being hijacked by this extension.What did you do? (Version 1)
test test
In insert mode selected
test
with the mouse, then pressed cmd-d and finally backspace.What did you do? (Version 2)
|test test
In insert placed cursor at start (represented here as a pipe), then pressed cmd-d twice and finally backspace.
What did you expect to happen?
| |
Two cursors (represented here as pipes)
What happened instead?
| test
With this extension enabled
cmd-d
does nothing in insert mode.This extension breaks theAdd Next Occurrence
command~~What did you do? ~~
test test
In insert mode selectedtest
with the mouse, selectAdd Next Occurrence
in the menu bar and then press backspace.What did you expect to happen?| |
Two cursors (represented here as pipes)What happened instead?| test|
With this extension enabledAdd Next Occurrence
adds a second bugged cursor to the right that does not behave like the first one (inconsistent behavior between attempts in spite of same sequence of keypresses).Technical details:
Needless to say, all of the above work properly and consistently with the extension disabled.
The text was updated successfully, but these errors were encountered: