![]() ![]() For me, the clue was the lock icon that is used by p10k configure. You could try to fiddle around with different values for the last byte to verify this theory. Taking your example of this results in 0x7C or | in ASCII. If a character is within that range, they effectively cut off the higher byte (value & 0xFF) to force it down into ASCII range. That range is ((value & 0xFFFFFE00) = 0xF000) and checked by the DIRECT_FONT macro. There is a range of unicode code points that is treated in a special way for some reason I haven't yet figured out. I have looked at the putty source code and found an interesting special case when rendering glyphs to the screen. This bug is specific to any font that uses a certain unicode code point range for its glyphs (from the fontawesome range in nerd fonts). ![]() Anyway I contacted the putty developers a few days ago (and haven't heard back from them yet) about a similar problem. ![]() I think I remember having read somewhere that putty and MobaXterm share a common code base, but I can't find it right now. Since I'm having a similar problem with putty, I'll share my findings here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |