alacritty: Screen corruption when using neovim
Sometimes I see screen corruption such as this when using neovim under WSL2. This is under tmux and TERM initially set to xterm-256color.
System
OS: Windows Version: alacritty 0.7.1 (a852eb8)
Logs
Crashes: STDERR, STDOUT
Font/Terminal size: alacritty -vv
[2021-01-11 11:11:33.222306500] [INFO ] [alacritty] Welcome to Alacritty
[2021-01-11 11:11:33.223305800] [INFO ] [alacritty] Configuration files loaded from: “C:\Users\hovna\AppData\Roaming\alacritty\alacritty.yml”
[2021-01-11 11:11:33.225306600] [DEBUG] [alacritty] Estimated DPR: 1.25
[2021-01-11 11:11:33.225306600] [DEBUG] [alacritty] Estimated window size: None
[2021-01-11 11:11:33.225306600] [DEBUG] [alacritty] Estimated cell size: 12 x 27
[2021-01-11 11:11:33.355577900] [INFO ] [alacritty] Device pixel ratio: 1.25
[2021-01-11 11:11:33.363578300] [INFO ] [alacritty] Initializing glyph cache…
[2021-01-11 11:11:33.364578400] [INFO ] [alacritty] … finished initializing glyph cache in 0.0013348s
[2021-01-11 11:11:33.365580400] [INFO ] [alacritty] Cell size: 12 x 27
[2021-01-11 11:11:33.365580400] [INFO ] [alacritty] Padding: 1 x 0
[2021-01-11 11:11:33.365580400] [INFO ] [alacritty] Width: 1024, Height: 768
[2021-01-11 11:11:33.380580500] [INFO ] [alacritty] PTY dimensions: Line(28) x Column(85)
[2021-01-11 11:11:33.383581900] [INFO ] [alacritty] Initialisation complete
[2021-01-11 11:11:33.385581000] [DEBUG] [alacritty_terminal] Term::resize dimensions unchanged
[2021-01-11 11:11:33.385581000] [INFO ] [alacritty] Padding: 1 x 0
[2021-01-11 11:11:33.385581000] [INFO ] [alacritty] Width: 1024, Height: 768
Keyboard and bindings: alacritty --print-events
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 4
- Comments: 16 (5 by maintainers)
I found the problem:
is causing the corruption.
I can reproduce it everytime. There is no corruption when i comment it out.
My setup:
No problem with other terminal emulators (e.g. Windows Terminal, wsltty) tho - like others said. I hope it helps with resolving the issue.
I will try it over this week. Thanks!