Ligatures are disabled, and yet it still converts => into ⇒
Which is neat if that's what you're after, but for me I like to see what the characters actually are, not what they imply.

| Micolithe |
|---|
| Agender |
| 36 years old |
| Philadelphia, PA |
![]() |
| Last Login: 08/30/2007 |
Agender Enby, Trans, Gay, AND the bearer of the gamer's curse. Not a man, not a woman, but instead I am puppy.
I got a fat ass and big ears.
--
Yes I did the cooking mama Let's Play way back when. I post alot about Tech (mostly how it sucks) and Cooking and Music and Television Shows and the occasional Let's Play video
💖@FadeToZac
--
We all do what we can ♫
So we can do just one more thing ♫
We can all be free ♫
Maybe not in words ♫
Maybe not with a look ♫
But with your mind ♫
Ligatures are disabled, and yet it still converts => into ⇒
Which is neat if that's what you're after, but for me I like to see what the characters actually are, not what they imply.
a) how dare you. ligatures are love, ligatures are life
b) no clue about mobaxterm, but most fonts offer a version without ligatures, and if not you can remove them yourself with fontforge
also this is probably not the case but just in case: did you type the ⇒ in the terminal or is that possibly an actual ⇒ unicode character lol
I typed it to test that the checkbox took effect (it did not)
Oringally I found it in a python script I was looking at w/ vim, it displays the ligature until I highlight one of the two characters at which point it splits it.
it may be you're running a vim or shell plugin that's doing the ligatures, I know there's one for vim
It's a personal preference thing, gimme that raw unconverted text
I wish you well in your ligature enjoyment.
they've bitten me a few times coding, so im using them but it's a trust but verify kinda situation