I used to want this too, until I thought about what it would be like to have a date/weekday change during waking hours for most of the world. I suspect that would cause even more problems than the timezone headaches.
About a year ago I posted a link to a collection of npm packages for use on the command-line, collectively called `themer`[1]. This link is to an offline-capable Progressive Web App that wraps the CLI packages and adds the capability to not only generate the themes but to more easily create your own set of colors with a tight feedback loop.
The PWA is open source[2] (as is the CLI, of course), features no ads/trackers/analytics (supported solely by Brave Rewards/$BAT), and takes advantage of PWA features like caching for offline use.
Thanks! I am the same way. Except rather than wasting time trying to find themes that support all the apps I use I wasted a ton MORE time building a tool to do it for me. Haha!
Solarized is fantastic. Perhaps I'm fickle, but I tend to like to change my theme every few months, and relatively few themes are as good as Solarized when it comes to supporting so many applications.
But I agree that the quick and simple install is a huge plus. Perhaps in the future theme authors could use a tool like themer to generate their themes rather than each author individually spending time figuring out how to apply their theme to a particular tool.
The reason why I not fully believe in it is that there is no huge benefit to the parties for supporting a thing like themer. UIs are highly custom and if X companies make a product seperately you will have as many implementations of the theme keys and variables.
The comparison to mobile development comes to mind. There are cross platform options like cordova or xamarin but they are usually beaten by native implementations. Now, if the cost of doing things twice outweights by large the drop in quality it is still a viable option; hence their existance. However, with themes I’d say the cost of redoing is most likely not outweighting developping in the native application option.
Good feedback. Yep, themer-terminal is for Terminal.app, the default macOS terminal. Feel free to log issues for supporting other terminals (or take a stab at implementing support for them as described at https://github.com/mjswensen/themer#create-your-own-template).