Save mark locations across sessions
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 quit vscode and enter again, all the marks are not working
To Reproduce
Steps to reproduce the behavior:
- Go to any place in your file and press m{a-zA-Z}
- Exit vscode and reopen your file, press '{a-zA-Z} or `{a-zA-Z}
- Notice the cursor has not moved and Error message E20: Mark not set
Expected behavior
I would expect the mark work
Screenshots
If applicable, add screenshots to help explain your problem.
If remapping-related, please attach log output: https://github.com/VSCodeVim/Vim#debugging-remappings.
Environment (please complete the following information):
- Extension (VsCodeVim) version:1.14.5
- VSCode version: 1.45
- OS: windows 10
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
The issue names VSCodeVim and the mark commands m{a-zA-Z}, '{a-zA-Z}, and `{a-zA-Z}, but no source file or test. Start by locating the mark-handling entry points and checking how extension state is managed across VS Code restarts. Done means marks remain available after reopening VS Code and both navigation commands work without E20.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100