Set key custom mappings for both normal and visual mode without duplication:
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Is your feature request related to a problem? Please describe.
It is a common case that we want the same mappings in normal and visual.
Is there a way to do that without duplication? E.g. currently I need:
"vim.normalModeKeyBindings": [
{
"before": [",", "e"],
"after": [":", "e", " "]
},
],
"vim.visualModeKeyBindings": [
{
"before": [",", "e"],
"after": [":", "e", " "]
},
],
Describe the solution you'd like
"vim.normalAndVisualModeKeyBindings": [
{
"before": [",", "e"],
"after": [":", "e", " "]
}
],
or perhaps:
"vim.modeKeyBindings": {
"modes": ["normal", "visual"],
"bind": [
{
"before": [",", "e"],
"after": [":", "e", " "]
}
],
Vim 1.24.3, vscode 1.74.2.
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 tracing how the vim.normalModeKeyBindings and vim.visualModeKeyBindings settings are parsed and applied. Confirm how a shared configuration would represent normal and visual modes, then verify that one mapping works in both modes without requiring duplicate entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- desktop, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100