Maxence Weynans

The custom linking going on under the hood seems like it could go sideways very fast. Custom elements used by plugins, semantics (granted, in some cases the default syntax files...

> some of the built-ins do the same (elflord, ron for instance, plus zellner has identifier and type with the same color) These don't count :smile: > As for custom...

The contrast between `Special` and `Normal`, `StatusLine` and `StatusLineNC`, `DiffChange` and `Difftext` seems too low to me, on both backgrounds. That's the only real complaint I have after a cursory...

I've been messing around with the light version this morning, made a few tweaks to better suit my taste, ended up reusing the palette of `quiet`, and I still wasn't...

> the active and inactive status lines are not easily distinguishable, I would suggest making one underlined (possibly the inactive one), I used to do that, but I'd often lose...

Slightly updated version, with changes to how StatusLineNC and Tabs are handled. Can't shake the bizarre way groups inherit the default vim colours. [None.zip](https://github.com/vim/colorschemes/files/4987341/None.zip)

If you're talking about the way the windows terminal uses different colours for bold characters, that's precisely what I'd hoped to avoid by only relying on foreground/background, and all of...

> Or is it "default-like" that depends on background of a host (GUI white, terminal whatever is there)? That's it. What it's set to effectively doesn't matter, the host process...

@lifepillar It's a catch-all solution for people working in busted environments that they don't have the privileges or the know-how to fix. It's overkill on purpose, as the only assumption...

> Imagine we get gruvbox at #1, now what? The project has been on life support for many years so how do we convince the author/maintainer/ghost to rewrite it with...