alacritty issue? - Githubissues

junegunn / goyo.vim

:tulip: Distraction-free writing in Vim

MIT License

4.49k stars 115 forks source link

alacritty issue? #200

Open xerron opened 5 years ago

xerron commented 5 years ago

is alacritty issue or goyo issue?

vimrc (~- vim) - VIM_012

junegunn commented 5 years ago

Possibly caused by some other plugin.

junegunn commented 5 years ago

Couldn't reproduce the problem on alacritty myself.

xerron commented 5 years ago

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

xerron commented 5 years ago

issue only in Vim + Alacritty

estysdesu commented 4 years ago

I do not have this issue with vim + alacritty

nixpulvis commented 4 years ago

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

estysdesu commented 4 years ago

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 commented 4 years ago

I have the same issue with alacritty.

Screenshot from 2019-09-21 19-18-20

while0pass commented 4 years ago

It depends on color scheme in some way:

while0pass commented 4 years ago

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

oschrenk commented 4 years ago

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 commented 1 year ago

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.