alacritty issue?

[xerron]

is alacritty issue or goyo issue?

[junegunn]

Possibly caused by some other plugin.

[junegunn]

Couldn't reproduce the problem on alacritty myself.

[xerron]

in neovim work fine in alacritty. but vim 8.1 not.

[xerron]

issue only in Vim + Alacritty

[estysdesu]

I do not have this issue with vim + alacritty

[nixpulvis]

@estysdesu that's good to hear. Out of curiosity what terminfo are you using (check using echo $TERM).

[estysdesu]

Alacritty visual preview:

$ echo $TERM
xterm-256color

Also, if you want to see my .vimrc, .alacritty.yml, or any other terminal settings you can likely find them in my dotfiles repo

[while0pass]

I have the same issue with alacritty.

[while0pass]

It depends on color scheme in some way:

[while0pass]

It is set termguicolors in my options that does the wicked job. But when off it obviously affects all the colors.

[oschrenk]

I have the same issue with gruxbox light.

I assume there is some timing issues because the color issues go away when I issue set background=light manually after Goyo is loaded.

[schmeisers]

A related issue I believe. Using alacritty. Invoking nvim then entering goyo with :Goyo works as expected with no artifacts or borders. However, nvim -c ':Goyo' results in the following error. After pressing ENTER, the borders are shown as in the screenshots above.