I just edited out the images because I thought it was my error but the active icon does not appear blue anymore.
I swapped multiple variables but it stays white/text color while only inactive tabs still color the icon. I guess this is
a work in progress thingy too so yeah

Hey @NullPlane, sorry but I don't understand what you're talking about, I only see a single image in the whole thread.

What's the active item?
Please let me know because I want to send a new release but if there's some blocker I won't.

 I guess this is a work in progress thingy too so yeah

It should be working though, it's working fine for the official themes.

I suspected it to be a problem on my part but I weren't sure bc I could not change it.
Active tab Icon color. I changed all keys connected to that but it stayed white.

Ah, I see, it's --tab-font-active, this used to be --menu-font-active, but I separated the colors from the menu for more flexibility.

tab:selected > tab::icon,
tab:not(:selected):hover > tab::icon {
	tint: var(--tab-font-active);
}

BTW: remember you can always add your own CSS rules. But in this case just changing that color will work (I tested it just in case hehe).

Oh yeah. The name is a little confusing haha I did not try it because I expected the literal font (<filename.ext>) to change.

BTW: remember you can always add your own CSS rules. But in this case just changing that color will work (I tested it just in case hehe).

That'd be great especially because I want to build my own theme however, I don't know any CSS at all. Everything webdev etc. is not my hobbyhorse; I am predominantly into research stuff and other than that, I consider whether I want to code a few specialized tools—that serve a very specific purpose only—more often and commit them to the internet. Stuff that I search the internet for hours just to not find anything. But mostly I don't start that because I solve these problems another more toilsome way that still consumes less time than coding from ground up and then, never need it again... Back in the day, I always argued when somebody made trash UIs or no UIs at all for very complex apps however, nowadays, I only do CLIs myself hehe so maybe I am going to learn Rust or Csharp someday or I am just going back to Pascal in case I ever have to do something like that because it is so rare.

Just don't use symbol, it's actually not a color, I should remove it because it's not being used although it could be used because it's listed... it's hard to explain without explaining you what symbol means in the language definition. If you're interested it's explained here, but in short symbol means that it should resolve a symbol which resolve to a color, if the symbol that was being resolved cannot be resolved, it will fallback to normal. A short example a pattern searchs for a symbol:
{ "pattern": "[%a_][%w_]*", "type": "symbol" }
from that pattern we will search to which symbol correspond the word matched:

  "symbols": [
    { "in": "keyword" },
    { "then": "keyword" },
    { "exit": "keyword" },
    { "alias": "keyword" },
    { "continue": "keyword" },
    { "getopts": "keyword" },

If the word isn't in the list, it fallback to normal, if is in the list the color is indicated in the specific word matched.

Sorry if I'm not being clear but in short, symbol is not a color although I've never removed it as a color, so you could technically use it as a color if you do:
{ "in": "symbol" }, that would resolve to the color declared in symbol.
Your confusion comes because those things are matching to other colors. IDK what you're doing anyways he.

Oh I now understand, I used "symbol" in the conversion table and it's in the documentation. Sorry, I trusted your documentation table too much, I didn't see the errors, let me fix them. In the conversion table we shouldn't probable use symbol (although symbol is almost always equal to normal in all color schemes, that's why it isn't an issue currently).

Addressed the confusion, now --icon uses normal. And updated docs.

Yea but instead of just deleting it out, it could be used for the purpose of "symbols" bc some ppl love when brackets have a different color than vanilla text. I just thought normal is asdf and symbol is []{}() etc. in regular code text with no special meaning such that e.g. in Python list[int, MyType] will have list and int colored as type and MyType is regular text normal as it is unknown as a type because we parse with patterns. Then, the [] around int, MyType could be colored with symbol.

That's how it looked because I could separately color brackets from the text however, text color changed by changing symbol while changing normal changed brackets color, that's where my confusion came from.

Why not leave it in for that purpose? More colors. However, you could also split special symbols but Ig that is just a hassle with the language definitions then. So it might have been on my end.

I can keep it no problem, the main "issue" is that it makes sense to have more colors if they are actively used the color schemes, and for that you need to use them in the language definition, otherwise they will not be picked at all. So it's not that simple if you really want to use them you'll need to modify the language definitions too.