Support for ' ' (Jump to previous cursor position)
See original GitHub issue- Click thumbs-up 👍 on this issue if you want it!
- Click confused 😕 on this issue if not having it makes VSCodeVim unusable.
The VSCodeVim team prioritizes issues based on reaction count.
In NeoVim or classic Vim I can jump back to my previous cursor position using ' '
. Which is usefull when I used Go to Definition (g d
) and want to jump back.
Is it possible to implement this feature?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:22
- Comments:11 (10 by maintainers)
Top Results From Across the Web
VIM: Jump Back To Previous or Last Cursor Position - nixCraft
To jump back forwards press CTRL-I (press and hold Ctrl key and press letter I).
Read more >How to go back to previous caret (text cursor) position?
Let's say I'm navigating by ctrl-clicking something and I get somewhere else in the same file ; how do I go back to...
Read more >notepad++: How to return to previous position? without mark ...
You can jump to any position that your cursor have been visited. Can use shortcut( ctrl + - for back position and ctrl...
Read more >Jump to previous cursor position functionality | Plex 2E
In Microsoft Visual Studio there is a shortcut key for navigating to last cursor position (ctrl + -). For example, if you look...
Read more >Is there a command that takes you back to previous cursor ...
It would be great if there were a command that allowed me to successively skip back to each previous cursor position in the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@cbosco No worries, all questions allowed.
I’m also not showing the correct behavior on my Mac on latest versions, and it seems that the extension owners are also not seeing the correct behavior. See the comments on PR #1993 from 2 days ago. It seems that we are waiting on an API command to be fully implemented in VSCode before this will work. You could pull a dev build of VSCode, but I recommend you simply wait until the next official release.
Fix in the pipeline: https://github.com/Microsoft/vscode/issues/36544