Lag for key mapping for move up one line

[mhz5]

Describe the bug
When c is mapped to k (move up one line) in Normal mode, pressing c has significant lag.

To Reproduce

• settings.json includes the setting: "vim.vimrc.enable": true
• .vimrc includes the mapping: noremap c k (c key moves up one line)
• In normal mode, press c c c. There is lag.

Expected behavior
There should be no lag.

Environment (please complete the following information):

• Extension (VsCodeVim) version:
• VSCode version: Bug introduced in 1.21.0
• OS: Mac 11.3.1

[pcwa-ahendricks]

Having a similar issue with one of my re-mappings after a recent update. In normal mode there is now a lag which didn't happen before.

   "vim.normalModeKeyBindingsNonRecursive": [
    {
      "before": ["d"],
      "after": ["p"]
    }
  ],

[waynewaynetsai]

We could set less delay time for remapped commands directly at settings.json.

[pcwa-ahendricks]

Setting that to 0 breaks a number of other commands as far as I can tell.

[waynewaynetsai]

Setting that to 0 breaks a number of other commands as far as I can tell.

Is there any github issue about it ?

[pcwa-ahendricks]

Setting that to 0 breaks a number of other commands as far as I can tell.

Is there any github issue about it ?

I'm not sure if that is necessarily a bug so there may be no issue for that one; it appears any remap that uses more that one character seems to not work with a 0 timeout value. Either way, I believe this issue relates to a breaking change that occurred after the 1.21.0 release. 1.20.3 didn't have this issue. The timeout setting existed during the 1.21.0 release when this wasn't an issue so I don't believe that to be the underlying cause.

[sql-koala]

see #6812
Looks like we need to create an option.

[pcwa-ahendricks]

Can this issue get labeled as a bug?