Stable Peek Setting not respected
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
VSCode Vim extension seems to be interfering with the Stable Peek setting which is especially bad for Vim users since typing escape is generally an idempotent action.
Steps to Reproduce:
- Enable vscodevim Extension
- enable Stable Peek setting
- Ctrl or cmd click a symbol to find references
- Hit ESC in the peek window
Expected Behavior:
The peek window stays open
Observed Behavior:
The peek window closes
Versions:
Version: 1.62.0 (Universal)
Commit: b3318bc
Date: 2021-11-03T15:24:41.297Z (5 days ago)
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0
VSCode: 1.21.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
Start by reproducing the behavior with the VSCodeVim extension and Stable Peek enabled, following the Ctrl/Cmd-click and Escape steps in the issue. Trace the extension's Escape handling during the peek interaction, and confirm the peek window remains open while Escape still behaves idempotently for Vim users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100