-
-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Neovim not working as expected #6425
Comments
Maybe it because the insert key isn't bound by default in neovim to enter insert mode (but the a key (like the i key) is). Have you tried another terminal before saying it's an issue with wezterm? |
yes i have, in the describe bug section it says that in iTerm is working as expected |
Oh yes sorry I didn't see it. I just tested on a Linux system and it indeed works as you'd expect, and neovim detects the key as Can you try in neovim (in command or insert mode) with Ctrl-v (not cmd-v) followed by the insert key? |
If i try Ctrl-v and then press Insert Key it switches to Visual Block. |
This is very weird..
From these logs, it's not actually the Insert that is detected by the terminal, it's instead detecting some other key that is not standard (see https://www.compart.com/en/unicode/U+F746 it's in the private area of unicode), in the key event we can see it's detected as I'm guessing this is MacOS-specific stuff, where the OS hijacks the usual Insert key on standard keyboards to do something else instead (probably showing some help in more traditional MacOS apps?). I'm not sure how iterm2 does interprets it as an actual insert key, 'cause the OS tells us it's not. |
I just tried both kitty and alacritty and it works just fine. |
i Jus try this configuration in the .wezterm.lua and it solves the issue with the insert key. But i do not know if this is intended.
|
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
20240203-110809-5046fc22
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
Current behavior
When i open neovim in wezterm, the Insert key is not working, not switching between modes. Also, if i press any other character, it automatically switches to insert mode and i can start typing.
Correct behavior
I have iterm and when i open neovim on it, if i press the insert key, then it switches between modes, and if i am in normal mode and i type any other character, i cannot start typing unless i am on insert mode from the Insert key.
To Reproduce
For Insert key issue
For any other character issue
Configuration
no config
Expected Behavior
For Insert key issue
For any other character issue
Logs
Logs for insert key
Logs for 'a' key
Anything else?
No response
The text was updated successfully, but these errors were encountered: