Open nnamdiogbu opened 6 months ago
Hi @nnamdiogbu! Thanks for this issue.
I am surprised that O
and V
are not working, they definitely should! What keyboard layout are you using? Do you have any custom keybindings defined?
Even once we fix that, not everything is there (yet!):
g e
is being implemented here: #7505 g ~
does not work and no-one is working on it that I know.If you'd like to pair with me on g~
(or just debugging why O
and V
don't work for you), please book time: https://calendly.com/conradirwin/pairing
Hi @ConradIrwin
I use the ANSI keyboard layout. No, I do not have any custom keybindings.
Regarding O
and V
, they only work when used with the shift
key. I had previously been using caps lock, and that was why it didn't work.
Since caps lock is not a modifier key, I cannot simply bind it to ToggleVisualBlock in assets/keymaps/vim.json. Is there some other way to perform this binding?
@nnamdiogbu I see! Currently we ignore the caps-lock key for the purposes of this.
You should be able to make this work by adding bindings to the upper-case versions of the keys to your keybindings. (You can see all vim bindings here).
{
"context": "vim_mode == normal && vim_operator == none && !VimWaiting"
"bindings": {
"O": "vim::InsertLineAbove",
// ... etc.
}
}
Is there a reason you use caps-lock instead of shift?
@nnamdiogbu I see! Currently we ignore the caps-lock key for the purposes of this.
You should be able to make this work by adding bindings to the upper-case versions of the keys to your keybindings. (You can see all vim bindings here).
{ "context": "vim_mode == normal && vim_operator == none && !VimWaiting" "bindings": { "O": "vim::InsertLineAbove", // ... etc. } }
Is there a reason you use caps-lock instead of shift?
This is a matter of habit, usually more commonly used lowercase letters, the temporary need for uppercase letters using shift, but it is true that people use caps to open the lock, cancel the lock after the input is complete!
I wanted to add that some IME software and Virtual Keyboards on Linux may affect this as well. I use IBus Wayland with KDE and this combo appears to break uppercase commands. Switching off the virtual input causes it to respond as expected.
Check for existing issues
Describe the feature
In the current implementation of the Vim mode in the text editor, I've encountered several issues with uppercase Vim commands not functioning as expected while in normal mode. Below are the specific observations:
Uppercase "O" Behavior:
Uppercase Vim Commands:
Additional Observations:
Vim mode is kind of unusable right now
If applicable, add mockups / screenshots to help present your vision of the feature
No response