TDE Devs, All,
There is an issue I've run into with Arch and the update of vim-9.2.0388 to vim-9.2.0437 that causes control codes "pp" to be shown in the vim window on the remote Arch host when accessed over ssh from my openSUSE KDE3/konsole (and from the Arch mailing list there are other terminals affected as well, such as one terminal on the RaspberryPi 5)
The terminal control codes provided by my terminal (as returned by v:termresponse in vim) are ^[[>0;115;0c which is also the same provided by the RaspberryPi 5 terminal reported on the Arch list.
There were no issue with vim up through vim-9.2.0388, but whatever the changes between that version and the new vim-9.2.0437 have caused the vim builtin xterm type to no longer play nicely with some older terminals.
If TDE hasn't patched or updated the konsole code in tdebase, then I would expect TDE/konsole to be impacted as well, thus this heads up so it can be looked into. If somebody running TDE also has an Arch box around, they can test/confirm this by:
1 open konsole, 2 ssh into the Arch box, 3 vim foo
If you see "pp" overlayed at the cursor position (first chars of a new file, or where the cursor is placed in an existing file), then TDE is impacted by this as well.
4 while still in vim, you can confirm the terminal response code by typing: 5 :echo v:termresponse (it will be shown bottom left over the command line)
We have a issue open with upstream, https://github.com/vim/vim/issues/20140 and we are working through patch ideas, etc.
So the purpose of this post was to provide a heads-up to TDE, and, of course, if you have a silver-bullet that solves this, I'll take that too :)
On 5/6/26 12:35 AM, David C Rankin via tde-devels wrote:
TDE Devs, All,
<snip>
So the purpose of this post was to provide a heads-up to TDE, and, of course, if you have a silver-bullet that solves this, I'll take that too :)
Whoop!
We don't need to hack konsole, this issue has been fixed upstream:
https://github.com/vim/vim/issues/20140
We were not the only one to notice:
https://github.com/vim/vim/issues/20156
Culminating in the pull request that solved the issue:
https://github.com/vim/vim/pull/20161