-
-
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
Jumping to Previous Position After Pressing a Key #9195
Comments
I have the same issue, |
CleanShot.2024-08-18.at.20.16.18.mp4 |
This bug exists for more than a year and was reported here: microsoft/vscode#177598 But it was closed after being identified as related to VSCodeVim. If there are any pointers or guidance on how to address this, please let me know—I'm happy to contribute if I'm able. This bug annoys me every single day. |
This is because {
"before": ["<C-o>"],
"commands": [
"workbench.action.navigateBack"
]
}, |
Hi @qazxcdswe123 I'm slightly confused about where It feels like cursor jumping from VSCode commands are not tracked by VSCodeVim - is it possible to have VSCodeVim somehow find where currently cursor is, in some circumstances, before moving cursors? |
As of your problem, I have no idea :( |
I have met the same issue at times, but it seems to work fine now, except in visual mode. |
In my "vim.handleKeys" setting, "<C-o>" is disabled, but the problem still rises |
Describe the bug
When searching for a symbol in VS Code, after finding the symbol and navigating to it, pressing any key on the keyboard causes the cursor to jump back to its previous position.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
After navigating to the symbol I want to go to, the cursor should not jump back to its previous position after pressing any key.
Environment
Additional context
This issue is not limited to searching for a symbol. If I also search for a word by pressing (Ctrl + F) and then navigate to that word, pressing any key causes the cursor to jump back to its previous position. This bug does not always occur, sometimes it doesn’t happen, and I’m still unsure what triggers it.
The text was updated successfully, but these errors were encountered: