`<C-o>` not working on many non-vim commands/jumps
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
C-o does not jump back after searching for refences or jumping to another location in another file through the explore etc.
To Reproduce
- put the cursor over a function
- right click and click
Find all references - click a location on in the results view
- press
C-o
also using pgup/pgdown/home does got get registered by the jumphandler
Expected behavior
expected to be returned back to the function definition, but instead it goes back to a previous jump i made.
also using pgup/pgdown/home does got get registered by the jumphandler
Is there a particular reason why we dont use vscode builtin Go Back / Go Forward commands? workbench.action.navigateBack / workbench.action.navigateBack
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
Start by reproducing the Find all references flow: select a result in the results view, then press C-o; also check whether PgUp, PgDown, and Home are recorded. Read the jump handler and compare its behavior with VS Code's workbench.action.navigateBack and workbench.action.navigateForward commands; done means these navigation actions return to the expected location.
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