Tags-like appearance for [INFO] [DEBUG] [TODO], similar to Maple Mono

[torindan]

• [ ] A programming language requires this ligation. Provide the information below.
• [ ] This ligation is implemented in other programming fonts. Provide samples below.

---

• AFAIK, no programming language requires it, but it looks nice in logs, or when editing some markdown status
• Maple Mono, and maybe Fira Code

I understand that it's mostly eye candy, but it would be nice

[be5invis]

This will, well, introduce many new glyphs... Impact will be thousands I think.

[torindan]

I might be saying stupid things here, but bear with me:

• the glyphs are already there, there are double width stuff like 🅸🅽🅵🅾
• so if it is possible to generate those as single width (or somehow reverse background/foreground for usual A-Z) and display them without spaces between characters, that might be enough + a semireversed version of '[' ']' with coloured inside
• and then just add a ligature rule for few strings ((9 from screenshot + '[todo]') * 2 for uppercase = 20, or configurable list of words) to use those reversed glyphs instead of regular glyphs

The feature might not be for everyone as no one wants array[i] to be rendered as array and i rendered as tag

[be5invis]

Well. Generating glyphs are easy, but it will produce over 1000 new glyphs into the font. Iosevka is already has 40,379 glyphs...

[be5invis]

And, guess what, the "negative circled/boxed letters/digits" is one of the biggest source of these glyph count. The glyph "❿" itself will produce around 500 glyphs.

[torindan]

whoa...i didn't know that...

feel free to drop the issue in backlog...and never see it again. iosevka is still my preferred font, appreciate all the effort

[Logo121]

And, guess what, the "negative circled/boxed letters/digits" is one of the biggest source of these glyph count. The glyph "❿" itself will produce around 500 glyphs.

I suppose what torindan meant is to substitute each character individually, like the tone modifiers ˥˦˧˨˩ which only change form depending on the character after (or before?) it instead of requiring all combination of 5^N tone combinations, so the number of variants from multiple characters won't really stack like ❿ or 🆜 does.

If we restrict the range of characters that can undergo a tag-like substitution to just the capital (ASCII) alphabet, then there would probably be no more than 300 new glyphs.

Or in the worst case, we can just make it opt-in or even incompatible with CV/Texture Healing on build...

Unless such kind of substitution is impossible, then nvm.

[be5invis]

@Logo121 The 1000 gid count is estimated using individual substitution already. Otherwise it might be over 10K...