conflicts with Ctrl + P to open files search dialog

[avelarpablo]

Type: Bug

Use Ctrl + P and the cursor will move to the upper line, instead of doing what is expected

Extension version: 1.26.0
VS Code version: Code 1.82.0 (8b617bd08fd9e3fc94d14adb8d358b56e3f72314, 2023-09-06T22:07:07.438Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Connection to 'wsl+Ubuntu-22.04' could not be established

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz (8 x 1190)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	15.69GB (3.32GB free)
Process Argv	--folder-uri=vscode-remote://wsl+Ubuntu-22.04/home/pavelar/dev/projects/hfh-app --remote=wsl+Ubuntu-22.04 --crash-reporter-id 66804790-da73-4e4e-af1e-681d53ccf0dd
Screen Reader	no
VM	0%

Connection to 'wsl+Ubuntu-22.04' could not be established

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30792227
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30803844
2e4cg342:30602488
f6dab269:30613381
showlangstatbar:30737416
0bi6i642:30835152
a2ce3375:30757347
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015cf:30829746

[xingholicqq]

The same problem, anyone knows how to solve this?

[spiffytech]

I've rolled rolled back the previous version, which still works:

Extensions -> Vim -> Gear -> Install Another Version -> 1.25.2

[aethnemitchell]

Same behaviour here since last update except ctrl-p will move cursor up 1 line (same as 'k').
I find if I tap 'alt' the intended behaviour will return.

[Luke-G-Cordova]

Adding the following to settings.json fixes this problem for me currently.

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

[terrybrash]

Adding the following to settings.json fixes this problem for me currently.

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

This breaks C-p in IntelliSense, which is supposed to move up one selection.

[shionryuu]

remove the vim keybinding in vscode

File -> Pereferences -> Keyboard Shortcuts -> Search 'Ctrl+p' -> Remove Keybinding

[MirKml]

Same, here. Above mentioned are workarounds I think.
The default extension settings should be to preserve CTRL+P as VS Code default - go to file. It's mostly used shortcuts I think 🙂
It can be configured to overload this. A specially when k is the 'idiomatic' vim. Who "Vimer" uses some CTRL + P for movements? ESC + k is the vim way 🙂 .

[SamHasler]

Duplicate of #8574

[albicasty]

I spent the morning with such issue, it is a nightmare.
As previously said, CTRL+P is both vscode default AND a vim extension to go to file.
Workarounds are ok.

[FaisalBudiono]

I spent the morning with such issue, it is a nightmare. As previously said, CTRL+P is both vscode default AND a vim extension to go to file. Workarounds are ok.

For now my current workaround is jus to downgrade to v1.25.2

[tudoanh]

I've rolled rolled back the previous version, which still works:

Extensions -> Vim -> Gear -> Install Another Version -> 1.25.2

Worked for me

[piotrwalczak1]

I confirm it's broken. This should be taken as top prio since Ctrp + P is the most used shortcuts in vscode. Breaks the whole idea of using this extension at all if this does not work.

[wswslzp]

I'm so surprised that this significant bug has no progress since Sep.

Maybe I'll never update VSCode VIM plugin from now.