Ctrl-v key bindings don't work in Windows Terminal

[rowanlovejoy]

Summary

The key binding for opening a file in a new vertical split (Ctrl-v) from the file picker doesn't work. The corresponding key binding for opening a file in a new horizontal split (Ctrl-s) does work. In Window mode, the key binding “v” for opening a new vertical split does work, but the Ctrl-v key binding doesn't.

I've noticed that if my clipboard contains text, if I press Ctrl-v in the file picker, it pastes the text from my clipboard into the fuzzy finder. This also happens if I use the Window mode Ctrl-v binding, my clipboard contents being pasted into the file. I think what might be happening is that the Windows paste key binding, which is also Ctrl-v, is overriding Helix's.

This issue occurs using any shell inside Windows Terminal. I have tried PowerShell, Command Prompt, and Git Bash.

My helix.log file is empty.

Using WezTerm on the same machine, the Ctrl-v key bindings work correctly, even if my clipboard contains text.

Reproduction Steps

I tried this:

1. Open the Windows Terminal
2. Navigate to a directory containing one or more files
3. Run 'hx' command
4. Open the file picker and select a file
5. Press Ctrl-v

I expected this to happen:

The selected file is opened in a new vertical split

Instead, this happened:

If my clipboard is empty, nothing happens. If my clipboard contains text, it is pasted into the fuzzy finder field.

Helix log

~/.cache/helix/helix.log

please provide a copy of `~/.cache/helix/helix.log` here if possible, you may need to redact some of the lines

Platform

Windows 10 (22H2)

Terminal Emulator

Windows Terminal 1.19.10821.0

Installation Method

Winget

Helix Version

helix 24.3 (2cadec0b)