Conflict with 'CTRL + P'
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
'CTRL + P' is an essential code navigation tool in native vscode. I really value being able to seemlessly navigate a codebase through the keyboard, as I'm sure many of us vim users can relate to.
Suddenly I find myself unable to use this amazing code navigation tool built in to vscode because VsCodeVim is now using it for seemingly no reason. This happened on both my PC and laptop yesterday so this has to have been some update.
Of course this was easy to rectify. Just delete the VscodeVim binding and you're all set. But having the extension's whole userbase all of a sudden have to identify and solve this problem seems ridiculous. To be honest I don't even know what vim's use for the binding is, but whatever it was it can occupy another keyboard binding.
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 Ctrl+P conflict in VS Code with the VsCodeVim extension enabled, then inspect the extension's keybinding configuration and the reported binding. Done means the native VS Code Ctrl+P navigation works without users having to delete the extension's binding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100