Bug 446214

Summary:	NeoVim versail split view glitch when scrolling
Product:	[Applications] konsole	Reporter:	Carl Schwan <carl>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	REPORTED ---
Severity:	normal	CC:	ninjalj
Priority:	NOR
Version:	master
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	video

Description Carl Schwan 2021-11-28 22:52:50 UTC

Created attachment 144049 [details]
video

SUMMARY

For approximately one month, my neovim doesn't work anymore with konsole. When using a vertical split view inside neochat and scrolling, the view gets broken.

Honestly, I'm not sure if this is a Konsole bug or a neovim bug. For the moment, I tried:

* compile old version of konsole (from last year) and use current version of neovim: still breaks
* use master version of konsole (the one I daily drive) with old version of neovim (0.3 and 0.4): still breaks
* reset all my settings in neovim: still breaks
* use neovim in xterm: works -> so maybe caused by konsole????
* A friend tried to reproduce and for him it works fine :/

This seems similar to https://github.com/neovim/neovim/issues/6802 but it's from 2017 and is now closed. My issue started appearing last month.  

Current workaround: use normal vim or use ctrl+l to refresh neovim. Both are not ideal since I use neovim autocompletion a lot

OBSERVED RESULT

Video in attachment

SOFTWARE/OS VERSIONS
Tried multiple things, see above. Currently using everything master including kwin (tried both wayland and kwin since it is a rendering bug)

Comment 1 ninjalj 2021-11-29 15:54:18 UTC

Konsole exports TERM=xterm-256color by default. For some time now, the terminfo entry for xterm-256color includes the smglr capability to set the left and right margins (a VT420+ feature). Konsole doesn't support left/right margins.

A possible workaround would be to export TERM=konsole-256color before starting neovim. The drawback to this is that connecting to hosts which have no terminfo/termcap entry for konsole-256color can cause strange issues: see for example https://bugs.kde.org/show_bug.cgi?id=431697 for an issue caused by connecting to a host with no entry for xterm-256color.