Conflict with 'CTRL + P'

[RiskExe]

'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.

[srackhall]

vim.mode == 'SearchInProgressMode'

I think it may be caused by the failure of this' when 'expression, but unfortunately, I don't know how to solve this problem. Because this shortcut key is still useful to me in search mode, I cannot handle this issue by deleting or modifying the shortcut key. I hope friends who are also facing this situation can provide some help.

[Panzer04]

The issue is that "suggestWidgetVisible" was removed from the old keymapping.

Previously the ctrl-p keymapping would apply what seems to be an up action when the editor was suggesting an autocomplete. Now, it's remapping it in all circumstances to up. It needs to be readded to fix the issue (or just remove? I don't really understand why it's present in the first place, but I am no Vim guru)

[ShadowManu]

Just an extra note in case anyone wonders how to quickly workaround this in the meantime, edit your settings.json file with:

{
  "vim.handleKeys": {
    "<C-p>": false
  }
}

[davdmoo]

I think the same issue has been mentioned in #8574