81–90 of 115 posts
Earlier quoted context omitted.
Yeah, only that it does that without any context. Ligature mishaps are doubleplus-unclean.
Not all ligatures work for all syntax files. Therefore the syntax file has something to do with ligatures, therefore it has context.
Earlier quoted context omitted.
Yeah it's great isn't it? I've tried heaps of times over the last few years to switch and haven't found a font I like better than Ubuntu Mono.
OT question: a lot of fonts come in all possible formats. If I am just installing them on my macOS box, does it matter which format I install? Is there a reason to prefer say .woff2 over .ttf? Or are they functionally equivalent?
Honest question: Why would you want ligatures in plaintext? Especially in code, wouldn't that be weird as some people tend to manually align their code? Like, modular_raft = 10 spam = 20 The "ft" in modular_raft should convert to a ligature so (I assume) it will then take one character, instead of two. Then developers viewing that source would have different alignments, depending on whether they use Sublime 3 or not.…
Some people use monospace fonts with ligatures specific to common programming languages: https://github.com/tonsky/FiraCode is one such example.
It's not a "must have", but I find it more readable and pleasing than using regular fonts.
Earlier quoted context omitted.
OT question: a lot of fonts come in all possible formats. If I am just installing them on my macOS box, does it matter which format I install? Is there a reason to prefer say .woff2 over .ttf? Or are they functionally equivalent?
woff and woff2 are web font standards. I don't think they're supported by most operating systems.
Earlier quoted context omitted.
I'm in the same boat as you (I'm also doing "git diff"manually from the command line before each commit). And to answer your question, probably for the same reason why people have moved on from Assembler to C to managed memory languages to JS and to today's JS frameworks, they want to avoid the "rough" parts by adding another layer of abstraction. For some people constantly going back to the terminal looks "rough", I…
> they want to avoid the "rough" parts by adding another layer of abstraction. They've also become thousands of times more productive.
It seems to work but it does render certain ligatures incorrectly on OS X for me. For example, ligature and <- is rendered as </. Since it's a dev build, I'm sure it will take some ironing out before it hits the stable version but this is really promising!
I believe this has now been fixed, although I've noticed a few other issues but the forum is down.
Earlier quoted context omitted.
woff and woff2 are web font standards. I don't think they're supported by most operating systems.
Well fair enough, but what about TTF vs OTF?
Yay! Now if only the TypeScript plugin were more reliable. Ligatures and TS support were the things making me consider switching. The TS plugin for Sublime is disappointingly buggy.
I think Sublime Text is very good but has fallen behind in terms of version control. I think Atom and VS Code are winning the war right now. Especially because the latter are free.
Honest question: Why would you want ligatures in plaintext? Especially in code, wouldn't that be weird as some people tend to manually align their code? Like, modular_raft = 10 spam = 20 The "ft" in modular_raft should convert to a ligature so (I assume) it will then take one character, instead of two. Then developers viewing that source would have different alignments, depending on whether they use Sublime 3 or not.…