Closed bynux-gh closed 4 days ago
in v7-beta4, this bug has been solved
Finally got the chance to actually test this out and (as of V7 Beta 24) it's beautiful. I love this font so much that I chose it for my hexadecimal/ASCII tattoo, so seeing that it's still a gorgeous work in progress makes me indescribably happy!
Best of all, this bug is fixed. ^^
As it currently stands, the ligature to change the "0x" of hexadecimal values only works if the succeeding characters (0-F) are capitalized.
0xFF
, for example, will become0×FF
, but0xff
will NOT become0×ff
. See thisdmesg
screenshot with memory addresses for an example:Expected behavior is that this ligature is applied even if the succeeding value is not capitalized, so long as it is a value between
'a'
((char) 0x61
) and'f'
((char) 0x66
).