Key mapped to leader can't be used as normal key in non-insert mode

• Click thumbs-up 👍 on this issue if you want it!
• Click confused 😕 on this issue if not having it makes VSCodeVim unusable.

The VSCodeVim team prioritizes issues based on reaction count.

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Environment:

• VSCode Version: 1.16.1
• VsCodeVim Version: 0.10.1
• OS: OSX 10.12.1

What happened: In settings.json, I have my leader mapped to a comma:

vim.leader: ","

Whenever I try to use a comma when navigating (f, or dt,), searching for a comma (/,) or in visual mode when the comma is pressed it is not treated as a normal key but as the leader and awaits the second key or chord.

What did you expect to happen: The leader functionality should only be activated when pressed first in normal and visual mode. If it follows after anything else, or in search mode, it should treated as a normal key

How to reproduce it:

• map a comma to the leader in user settings
• go to any code and try to navigate to the closest comma (f, or t,) or try to search for a comma (/,)

[gallor]

Well don’t I feel silly. 😃 I didn’t realize I needed to map those using the vim.otherModesKeyBindingsNonRecursive setting. Thanks

[xconverge]

These are the problem ones for you 😉 feel free to reopen if you continue to have issues

{
        "key": ", l",
        "command": "workbench.action.focusNextGroup",
        "when": "editorTextFocus && vim.active && vim.mode != 'Insert'"
    },
    {
        "key": ", h",
        "command": "workbench.action.focusPreviousGroup",
        "when": "editorTextFocus && vim.active && vim.mode != 'Insert'"
    },