-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
I'm a little puzzled as to why they'd do that. It's completely possible to use the :colorscheme command.
that's what I did because of the problem described by OP, I just created a repo with my own versions of the themes I like and each variant is just a new theme instead of having to created a logic where the background or whatever changes depending on an option. Originally I took the inspiration from hlissner/emacs-doom-themes where each variant of a theme its just an entire new theme and you don't have to play with global variables. And this approach was better for me because I can do my own tweaks and not necessarily make the theme look exactly like the original one.
I like your idea so much that I'm gonna look into implementing it in the ayu branch I currently maintain (https://github.com/Luxed/ayu-vim). I'm not a fan of it for some reason, but I agree with what it brings. I could argue that the theme has other options anyway, so you'll most likely need somewhere to put those too. But I'll at least look into it
I understand and share OPs frustration and I have tried to keep things as simple as possible in my implementation of Solarized out of pure frustration. IMO there are two things to consider:
Hey, thanks for the reply. I just pushed my attempt at a colorscheme switcher to https://github.com/metalelf0/witch-nvim. I'd be glad if you shared your opinion about it!