Even simply adding "-light" and "-dark" to the colour scheme name would be useful, but it needs to be agreed and applied consistently.

If going that way, there might just as well be a [theme_info] mood=dark property...
Otherwise, maybe a very simple and naïve test such as "check if named_styles.default[1] starts with a number"¹² could work for unclassified tests (except for some corner cases. It works for every colorscheme in geany_themes at least.) But I can see how that may end up going down a rabbit hole of corner cases.
(Or if it won't cause much trouble, actually compute and compare foreground and background luminance using a simplified R'G'B'→Y formula; but I suspect that's asking for a lot).

So let the 🚲 🏠 begin ...

OK, I give up 😄 "Let the ride home begin"? "Let the cycle building begin"?

I would also recommend getting your computer glasses checked (makes note for self to do so ...).

I don't use glasses. Not yet at least. Maybe I should get checked to see if I should...

More precisely, check whether it starts with #+number, or if it starts with a letter (named color) and named_colors[named_styles.default[1]] starts with #+number. ↩
Here I am naïvely assuming that a light theme won't use a color with a low R value but high G and B ones, like #9FFFFF. ↩

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Footnotes