[vim/vim] Cannot map Ctrl-I in terminal mode when using modifyOtherKeys (PR #16558)

10 views
Skip to first unread message

zeertzjq

unread,
Feb 1, 2025, 3:29:50 AM2/1/25
to vim/vim, Subscribed

Problem: Cannot map Ctrl-I in terminal mode when using modifyOtherKeys
(after 9.0.0912).
Solution: Convert letters with Ctrl modifier to upper-case in input
buffer, and convert them back to lower-case in libvterm.


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/16558

Commit Summary

  • d3ef1a8 Cannot map Ctrl-I in terminal mode when using modifyOtherKeys

File Changes

(2 files)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558@github.com>

zeertzjq

unread,
Feb 1, 2025, 3:32:30 AM2/1/25
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • 0dd2367 Cannot map Ctrl-I in terminal mode when using modifyOtherKeys


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/before/d3ef1a8013392ce0bc2404c04f5b4354a55800ac/after/0dd2367179bfa1d28e054c6c42949051a6895afd@github.com>

zeertzjq

unread,
Feb 1, 2025, 4:06:52 AM2/1/25
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • c3349b4 Cannot map Ctrl-I in terminal mode when using modifyOtherKeys

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/before/0dd2367179bfa1d28e054c6c42949051a6895afd/after/c3349b488bb684b5c01ae0cd4515b0c433ba76ed@github.com>

zeertzjq

unread,
Feb 1, 2025, 7:57:37 AM2/1/25
to vim/vim, Subscribed

I've been trying hours to write a test for this, but it has always been extremely flaky.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/c2628943511@github.com>

zeertzjq

unread,
Feb 1, 2025, 8:29:45 AM2/1/25
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • 0e8f9e5 Cannot map Ctrl-I in terminal mode when using modifyOtherKeys

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/before/c3349b488bb684b5c01ae0cd4515b0c433ba76ed/after/0e8f9e511d1381681b6dee9c55dc94a613edd39c@github.com>

zeertzjq

unread,
Feb 1, 2025, 8:57:24 AM2/1/25
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • fbbc8e0 Cannot map Ctrl-I in terminal mode when using modifyOtherKeys

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/before/0e8f9e511d1381681b6dee9c55dc94a613edd39c/after/fbbc8e0c0140e0b2efdf4eb570f5ea9e54265c06@github.com>

zeertzjq

unread,
Feb 1, 2025, 9:04:44 AM2/1/25
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • cb4285a Cannot map Ctrl-I in terminal mode when using modifyOtherKeys

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/before/fbbc8e0c0140e0b2efdf4eb570f5ea9e54265c06/after/cb4285a59db7efd62001ef8cafd73a70e30a607f@github.com>

zeertzjq

unread,
Feb 1, 2025, 9:19:31 AM2/1/25
to vim/vim, Subscribed

I'm not entirely sure about this PR. If (hypothetically) there is a terminal that sends Ctrl-i and Ctrl-I (both without Shift modifier) for two different key combinations, this PR will make Vim treat these two as the same. However Vim already treats these two as the same in non-Terminal mode, so maybe this still makes sense.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/c2628970859@github.com>

zeertzjq

unread,
Feb 1, 2025, 9:21:47 AM2/1/25
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • f9d31f0 Cannot map Ctrl-I in terminal mode when using modifyOtherKeys

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/before/cb4285a59db7efd62001ef8cafd73a70e30a607f/after/f9d31f03a3b7eb18dae85df210a664c7da06d001@github.com>

zeertzjq

unread,
Feb 1, 2025, 9:40:31 AM2/1/25
to vim/vim, Subscribed

Oh, that can actually happen in XTerm when Caps Lock is on. This may need more consideration then.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/c2628978410@github.com>

Christian Brabandt

unread,
Feb 1, 2025, 9:51:54 AM2/1/25
to vim/vim, Subscribed

Oh, that can actually happen in XTerm when Caps Lock is on. This may need more consideration then.

Oh, it doesn't send Shift-modifier even with xterm-modifier keys enabled?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/c2628982144@github.com>

zeertzjq

unread,
Feb 1, 2025, 9:56:48 AM2/1/25
to vim/vim, Subscribed

If you mean modifyOtherKeys level 2, when Caps Lock is active, Ctrl-I sends \x1b[27;5;73~, which doesn't include the Shift modifier. In comparison, when Caps Lock is off, Ctrl-Shift-I sends \x1b[27;6;73~, which includes the Shift modifier.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/c2628983796@github.com>

Christian Brabandt

unread,
Jun 13, 2026, 4:15:15 PM (10 hours ago) Jun 13
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#16558)

this has stalled, so closing


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/16558/c4699664433@github.com>

Reply all
Reply to author
Forward
0 new messages