: to enter a command.ˊ should be printed.This bug might be exclusive to French AZERTY keyboard layout.
The enter key should make a new line in insert mode, or executed the command prompted by the user.
9.0.1632-2.1
OS: OpenSUSE Tumbleweed
Terminal: kitty 0.29.2
$TERM: xterm-kitty
Shell: Fish, same behavior on Bash.
Keyboard layout: French AZERTY (Might be relevant to the issue).
My Vim is completely default.
I have also posted an issue about it on kitty git, and the maintainer indicated me that this must be an issue with how the Kitty Keyboard Protocol is implemented in Vim.
Kitty issue #6527
No response
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
When I press enter it is switching from insert mode to escape mode. I turned off num lock after that it started to work fine.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I have the latest stable release of the kitty terminal emulator and of the fish shell, as well as the latest commit of Vim:
$ kitty --version
kitty 0.29.2 created by Kovid Goyal
$ fish --version
fish, version 3.6.1
$ vim --version | head --lines=2
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Aug 8 2023 20:10:05)
Included patches: 1-1678
I also have an AZERTY keyboard. But I can't reproduce this issue; neither with nor without config (--clean). Not saying that there is no issue; just that something might be missing from the report for other people to reproduce.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
There may be a bug in the keyboard itself. Although the same thing should happen when pressing the keypad Enter key on a full keyboard.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Greetings, for a bit of extra context on this issue, I also have another issue opened over on neovim with a different behaviour: Neovim issue #24577, where a workaround has been found using a simple remap.
I haven't tested yet to do the same on regular vim, but I think this should be a good workaround on vim as well. I'll try to do that after work.
@zeertzjq Made me perform the same test in GVim, which resulted in the same behavior as neovim.
Since then I encounter yet another situation where that key cause issue, using one of kitty's default keybindings (ctrl+shift+enter to open a new tiled window), which was also solvable with a remap. All that leads me to think that as @zeertzjq suggests, a keyboard bug is the most likely cause, but I don't know how to fully confirm this.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
okay, let me close it for now then. Thanks!
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Closed #12731 as not planned.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Hello again, I can confirm that using a remap as a workaround. This is what I used in my vimrc in case anyone encounters the same issue:
nmap <Enter>
vmap <Enter>
imap <Enter>
cmap <Enter>
I thank everyone for their time. Positive thoughts for Bram, all Vim contributors and his loved ones.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()