You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 become 0×FF, but 0xff will NOT become 0×ff. See this dmesg 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).
The text was updated successfully, but these errors were encountered:
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
).The text was updated successfully, but these errors were encountered: