On 5/5/26 4:28 PM, Pocket wrote:
Pocket,
after you open vim, what does:
:echo v:termresponse
show? It will be something like "^[[>0;115;0c" (mine). Let me know and
I'll add that to the bug report.
^[[>0;115;0c
The problem is a patch to vim /src/term.c:
diff --git a/src/term.c b/src/term.c
index 37f05ed01..300d503b0 100644
--- a/src/term.c
+++ b/src/term.c
@@ -5173,7 +5173,7 @@ handle_version_response(int first, int *arg, int
argc, char_u *tp)
// libvterm sends 0;100;0
// Konsole sends 0;115;0 and works the same way
- if ((version == 100 || version == 115) && arg[0] == 0 && arg[2]
== 0)
+ if ((version == 100) && arg[0] == 0 && arg[2] == 0)
{
// If run from Vim $COLORS is set to the number of
// colors the terminal supports. Otherwise assume
That removed recognizing terminals that report 115.
Thank you, that was the exact same terminal code I have from the
KDE3/konsole when ssh'ed into Arch running vim.
I should clarify, the above patch was one proposed to fix the issue by
the vim developers. I built from
https://gitlab.archlinux.org/archlinux/packaging/packages/vim adding the
patch, and it didn't fix the issue. Work is ongoing.
I also reproduced your arrow-key issue (I think). When I use 'vim -T
vt320' pressing up-arrow invokes input mode and inserts an 'A' each time
the key is pressed and then down-arrow key inserts a 'B'. Now that is
likely just the mismatch between the builtin and what the terminal
supports, but if you are seeing similar behavior without altering the
-T, that points to the same type mismatch with the new term.c changes in
vim.
Thank you for confirming the v:termresponse codes.
Staying on vim 9.2.0388 works for now, as does building from AUR
vim-classic-git which is the continuation of the 8.2 branch. I have that
on one machine now.
--
David C. Rankin, J.D.,P.E.
