daa84 / neovim-gtk

gtk ui for neovim
GNU General Public License v3.0
716 stars 56 forks source link

Bug : Suddenly colorschemes aren broken #96

Closed Zardoz89 closed 6 years ago

Zardoz89 commented 6 years ago

The last commits (not hapens on commit bda35ef ) has broken vim colorschemes :

This happens with monokai-phoenix and with darkblue (included on all vim/neovim) color scheme

To reproduce :

" Color mode
if (has("termguicolors"))
  set termguicolors       " TrueColor!
else
  set t_Co=256            " 256 color mode in term
endif

set background=dark
" colors monokai-phoenix
colors darkblue

Monokai-phoenix: monokai-phoenix

Darkblue: darkblue

daa84 commented 6 years ago

Ah, looks like problem only when NVIM_GTK_DOUBLE_BUFFER=1

Zardoz89 commented 6 years ago

@daa84 It isn't fixed! Keep happening with the last commit.

daa84 commented 6 years ago

did you use NVIM_GTK_DOUBLE_BUFFER=1 ?

themayarose commented 6 years ago

I experience this issue with both NVIM_GTK_DOUBLE_BUFFER on and off.

EDIT: This happens on commits 544 and 545; on 542 it's working fine.

Zardoz89 commented 6 years ago

@daa84 I just try with the last commit and with NVIM_GTK_DOUBLE_BUFFER=1 . Works correctly. imagen

@ugopozo Better try to paste commit hash instead of numbers.

daa84 commented 6 years ago

@Zardoz89 c56c945f025a9350a8e99ab4b77c447ff35f9966 does change something? NVIM_GTK_DOUBLE_BUFFER=0 does not work?

themayarose commented 6 years ago

On c56c945 (commit 546) NVIM_GTK_DOUBLE_BUFFER=1 fixes the issue. Yay!

However, with the double buffer set to zero, the colors still appear off. But IIRC the double buffering setting is supposed to force the default behavior when for some reason it's disabled, right? So maybe it can be considered fixed for now.

daa84 commented 6 years ago

NVIM_GTK_DOUBLE_BUFFER do some small performance impact. Also in my local installation i don't have any problems without NVIM_GTK_DOUBLE_BUFFER, so it is disabled by default 😄 But maybe it is good idea to enable it.

Zardoz89 commented 6 years ago

@Zardoz89 c56c945 does change something? NVIM_GTK_DOUBLE_BUFFER=0 does not work?

Keeps happening.

NVIM_GTK_DOUBLE_BUFFER do some small performance impact. Also in my local installation i don't have any problems without NVIM_GTK_DOUBLE_BUFFER, so it is disabled by default smile But maybe it is good idea to enable it.

But, why this happening ? Why disabling/enabling double buffering affect this ? It's related to a Gtk bug ?

daa84 commented 6 years ago

Looks like gtkdrawingarea surface in some configurations (or gtk version) created without alpha channel. Don't know why.

YaLTeR commented 6 years ago

Also started hitting this issue, NVIM_GTK_DOUBLE_BUFFER=1 seems to fix it.

maorv commented 6 years ago

reverting below commit seems to fix the issue (at least on ubuntu 18.04)

commit 2dc10aa6110aa17d72554c82c9f0676f3d5609a2 Merge: df04e7d 8216cfb Author: daa andrey.dubravin@gmail.com Date: Sun May 6 13:00:21 2018 +0300

Merge branch 'cursor-color' (#43)
daa84 commented 6 years ago

NVIM_GTK_DOUBLE_BUFFER removed with 21e74c7ca7468a53ce1cbb449a19b8144f06836f , must issue must be fixed