[vim/vim] ~ randomly and transiently stops working on kitty (Issue #16651)

hseg

unread,

Feb 16, 2025, 7:33:20 AMFeb 16

to vim/vim, Subscribed

Steps to reproduce

Start with kitty --config NONE vim --clean
Try typing ~ repeatedly
Usually, this works, and you obtain a line of ~.
However, every so often (~30% of the time) an audible bell sound is played and (as is visible if the buffer contains some text) the cursor jumps a few lines down, as if <PageDown> was typed.
Testing with <CTRL-V>~ gives ~, but <CTRL-K>~ gives <kPageDown> (my keyboard has ~ as ``<Shift->, hence the shift modifier is unavoidable here).
When I ran into this problem originally, ~ would delete a whole chunk of text downwards, but I can neither reproduce it right now nor can recall the details well enough to reconstruct it. It occurred when vim was invoked as EDITOR by git commit in that instance.

Expected behaviour

~ should behave in insert mode as any non-control character -- typing it should just insert U+007E -- and it should get to participate in digraphs (eg ñ is mapped on my system as n~).

Most importantly, though -- this behaviour should be consistent. This last point it the most confusing to me.

Version of Vim

9.1.1065

Environment

Operating system: Arch Linux
Terminal: kitty 0.39.1
TERM: xterm-kitty
Shell: bash 5.2.37(1)-release

Logs and stack traces

# I thought passing --dump-commands to kitty would help, but this is all it prints on typing ~:
screen_bell
screen_reset_mode 25 1
screen_set_mode 12 1
screen_set_mode 25 1

# The following is emitted by kitty in all circumstances
[0.214] [glfw error 65544]: process_desktop_settings: failed with error: [org.freedesktop.DBus.Error.ServiceUnknown] The name is not activatable
[0.258] [PARSE ERROR] Unknown DCS escape code: zz
[0.258] [PARSE ERROR] Unknown CSI code: 'm' with start_modifier: '␀' and end_modifier: '%' and parameters: '0'
[0.258] [PARSE ERROR] Unknown terminfo property: RGB
[3.617] The application is trying to use xterm's modifyOtherKeys. This is superseded by the kitty keyboard protocol https://sw.kovidgoyal.net/kitty/keyboard-protocol. The application should be updated to use that.
[3.617] The application is trying to use xterm's modifyOtherKeys. This is superseded by the kitty keyboard protocol https://sw.kovidgoyal.net/kitty/keyboard-protocol. The application should be updated to use that.
# note the messages at 3.617 are printed at teardown. It'd be nice not to get these warnings

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

hseg created an issue (vim/vim#16651)

Steps to reproduce

Start with kitty --config NONE vim --clean
Try typing ~ repeatedly
Usually, this works, and you obtain a line of ~.
However, every so often (~30% of the time) an audible bell sound is played and (as is visible if the buffer contains some text) the cursor jumps a few lines down, as if <PageDown> was typed.
Testing with <CTRL-V>~ gives ~, but <CTRL-K>~ gives <kPageDown> (my keyboard has ~ as ``<Shift->, hence the shift modifier is unavoidable here).
When I ran into this problem originally, ~ would delete a whole chunk of text downwards, but I can neither reproduce it right now nor can recall the details well enough to reconstruct it. It occurred when vim was invoked as EDITOR by git commit in that instance.

Expected behaviour

~ should behave in insert mode as any non-control character -- typing it should just insert U+007E -- and it should get to participate in digraphs (eg ñ is mapped on my system as n~).

Most importantly, though -- this behaviour should be consistent. This last point it the most confusing to me.

Version of Vim

9.1.1065

Environment

Operating system: Arch Linux
Terminal: kitty 0.39.1
TERM: xterm-kitty
Shell: bash 5.2.37(1)-release

Logs and stack traces

# I thought passing --dump-commands to kitty would help, but this is all it prints on typing ~:
screen_bell
screen_reset_mode 25 1
screen_set_mode 12 1
screen_set_mode 25 1

# The following is emitted by kitty in all circumstances
[0.214] [glfw error 65544]: process_desktop_settings: failed with error: [org.freedesktop.DBus.Error.ServiceUnknown] The name is not activatable
[0.258] [PARSE ERROR] Unknown DCS escape code: zz
[0.258] [PARSE ERROR] Unknown CSI code: 'm' with start_modifier: '␀' and end_modifier: '%' and parameters: '0'
[0.258] [PARSE ERROR] Unknown terminfo property: RGB
[3.617] The application is trying to use xterm's modifyOtherKeys. This is superseded by the kitty keyboard protocol https://sw.kovidgoyal.net/kitty/keyboard-protocol. The application should be updated to use that.
[3.617] The application is trying to use xterm's modifyOtherKeys. This is superseded by the kitty keyboard protocol https://sw.kovidgoyal.net/kitty/keyboard-protocol. The application should be updated to use that.
# note the messages at 3.617 are printed at teardown. It'd be nice not to get these warnings

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

chdiza

unread,

Feb 17, 2025, 7:41:25 AMFeb 17

to vim/vim, Subscribed

chdiza left a comment (vim/vim#16651)

I am also gettting weird and random behavior from "~" in kitty. I have not been able to nail down a reproducer.

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

julio-b

unread,

Feb 18, 2025, 6:18:01 PMFeb 18

to vim/vim, Subscribed

julio-b left a comment (vim/vim#16651)

I ran into the same problem about a week ago.

Version of Vim

9.1.1065

Are you still able to reproduce the issue after v9.1.1082 ? This patch should resolve it, please let me know if it doesn't.

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Maxim Kim

unread,

Feb 18, 2025, 8:32:46 PMFeb 18

to vim/vim, Subscribed

habamax left a comment (vim/vim#16651)

[3.617] The application is trying to use xterm's modifyOtherKeys. This is superseded by the kitty keyboard protocol https://sw.kovidgoyal.net/kitty/keyboard-protocol. The application should be updated to use that.

The application should be updated to use that.

Or terminal should be updated to supersed xterm's modifyOtherKeys in a way it works with vim? Idk.

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

hseg

unread,

Feb 19, 2025, 10:19:11 AMFeb 19

to vim/vim, Subscribed

hseg left a comment (vim/vim#16651)

Indeed, after updating to vim 9.1.1120 the problem appears to have disappeared.
As far as I'm concerned, this can be closed.

(The log messages are still there, but that's an innocuous issue suited for a
different ticket)

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Feb 19, 2025, 10:42:03 AMFeb 19

to vim/vim, Subscribed

Closed #16651 as completed.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Reply all

Reply to author

Forward