Niklas Haas

Update: re: “how was it ever working for me before?” I seem to have found the culprit: I had a Vertex-Dark git clone in my `dev` folder, left on commit...

Another thing I forgot to point out: It actually works fine in `gtk-theme-switch`'s “Preview” dialog, and ONLY there. 

The issue grows more mysterious: I checked out yesterday's FS snapshot (when it was still working fine) and had a dig through `/usr/lib64/gtk-2.0` - and there was not a trace...

Okay, I managed to fix it. I went through and downgraded all of the suspect packages one by one to their version from yesterday, reinstalled the `/usr/share/themes/Vertex*` folders from the...

Huh, that's odd: Apparently my issues resume the moment I install `gnome-themes-standard`. (Before, I did not have this package installed at all, it seems to have pulled in by `gtk+-2.24.31-r1`,...

Hmm, it seems I got excited too quickly. While my issue is resolved for `gtk+:2`, my `gtk+:3` issue remains. It seems I can only solve it by removing `vertex-theme` entirely...

I don't think you explained the issue well. But you also ignored the issue template, so...

After switching buffers, no proper highlighting: ``` Highlighting for buffer 23 Updating from cache silent! syntax clear _Neotags_c_d_cPreProcTag | syntax keyword _Neotags_c_d_cPreProcTag VK CHECK PL_DEF PL_ERR PL_MAX PL_MIN PL_INFO PL_WARN...

In case it helps, I usually switch buffers using the `ctrlp` extension, which is what I think has the highest rate of triggering this issue? Sometimes switching between different split...

Does it work with glslang instead of shaderc?