VSCodeVim / VSCodeVim/Vim

Marks are reset/removed after some time

Open
#3,841 14 comments 22 reactions 0 assignees View on GitHub

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
I work on a file, set some marks for key areas I jump around between. After a while I notice that my marks are gone, this is happening repeatedly while working with the file.

To Reproduce
Steps to reproduce the behavior:

  1. Go to a file
  2. Set a couple of marks
  3. Continue to use the application, work for some time (maybe an hour? not quite sure)
  4. Try to go to previously set mark, it is now no longer there. Error message E20: Mark not set

Expected behavior
Got to the previously set mark

Screenshots
If applicable, add screenshots to help explain your problem.
If remapping-related, please attach log output: https://github.com/VSCodeVim/Vim#debugging-remappings.
N/A

Environment (please complete the following information):

  • Extension (VsCodeVim) version: 1.8.1
  • VSCode version: Version 1.34.0 (1.34.0)
  • OS: macOS 10.14.5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in VSCodeVim using the reported steps: set marks in a file, continue working for about an hour, and try to jump to them. Investigate the mark handling and persistence entry points, then verify that previously set marks remain available instead of producing E20: Mark not set.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.