`<C-o>` doesn't work
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
CTRL+O behavior is strange and it doesn't work as expected
To Reproduce
Steps to reproduce the behavior:
- Go to any 0.ts file
- Find a definition for any method and go to 1.ts file, then find a definition for another method and jump to 2.ts file
- Press ctrl+o
Expected behavior
I expected to travel back in history to 1.ts, then to file 0.ts.
Actual behavior
Sometimes, it skips 1.ts and just jumps back to 0.ts, sometimes it does nothing at all. So I have no idea where will I come after pressing CTRL+O
Environment (please complete the following information):
- Extension (VsCodeVim) version:1.1.0
- VSCode version: 1.32.3
- OS: tried on both latest MacOS and Ubuntu 18.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
No files or tests are named. Reproduce the Ctrl+O behavior in VSCode using the listed multi-file definition jumps, then trace the VSCodeVim history handling; done when Ctrl+O consistently returns from 2.ts to 1.ts and then 0.ts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100