Cursor position incorrect after jumping to a global mark
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
When I navigate to an uppercase (global) mark in another file, vscode opens the file but does not set the cursor position correctly. (The cursor stays in its previous position.) Navigating to the mark a second time fixes the issue.
To Reproduce
Steps to reproduce the behavior:
- Set an uppercase mark in a file (with
mAfor example) - Move the cursor to another line in the file
- Open a different file
- Navigate to the mark (with
'Afor example)
Expected behavior
The cursor should move to the marked line on the first invocation.
Screenshots
https://user-images.githubusercontent.com/702318/191124071-4d0f3848-405e-49f4-a77b-2f6f7fec4173.mov
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.23.2
- VSCode version: 1.71.2
- OS: macOS 12.6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the four listed steps in VSCodeVim using the stated extension and VS Code versions. Trace the global-mark navigation behavior, then verify that navigating to a mark in another file places the cursor on the marked line during the first invocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100