Monospaced Programming Fonts with Ligatures

Post by amk_ » Fri, Jul 21, 2017, 8:24 PM UTC

masklinn wrote: post #86

gervase wrote: post #66

Earlier quoted context omitted.

I assume potential sarcasm would be related to the difficulty differentiating between similar symbols, based on length, with different lexicographic meanings. For example, dash vs endash vs emdash, etc: ‒ – — ― If those symbols were used in a programming language and had different meanings, differentiating quickly could be much more difficult than seeing the difference between -, --, ---, and so on at a glance.

> the difficulty differentiating between similar symbols, based on length, with different lexicographic meanings. The very thing amk_ is praising is that this issue is fixed in both Fira and Monoid by the triple-equal being not just longer but represented using 3 horizontal bars rather than just 2.

Post by armagon » Fri, Jul 21, 2017, 8:27 PM UTC

mcbits wrote: post #144

edejong wrote: post #33

Apparently I'm one of the two users of proportionality spaced fonts for coding. I've used this now for five years and I don't understand why developers still see this need to code as if monospaced terminals is all that's available. Especially on large screens with high dpi it reads much faster. It also makes it less awkward to use editor unicode substitution for display purposes.

I also prefer proportional fonts, but some people's "ASCII artsy" programming styles, along with editors themselves, make it hard to use readable fonts in practice. What I would like is a language-aware editor that can visually align assignments, parameters, etc. without touching the actual whitespace characters. You get 1 tab for indentation (if the language allows tabs) and 1 space for alignment, and the editor tak…

Post by 21 » Fri, Jul 21, 2017, 8:35 PM UTC

Avshalom wrote: post #155

mathgenius wrote: post #103

Earlier quoted context omitted.

> For example, it cured the bad habit I had of lining too many things up in columns I don't like this style either, but it's a style not a "bad habit."

nah, it's a bad habit. It means constant readjustment and unnecessarily bloated diffs every time you change a function or variable name. or the lovely foo := a; bar := b; then a day later foo := a; bar := b; foobar := cd; which also points to the problem that it lends itself to premature constant readjustment because a day later you have to move every thing again because as it turns out you really needed foobarlist a…

Post by amk_ » Fri, Jul 21, 2017, 8:41 PM UTC

gervase wrote: post #66

masklinn wrote: post #24

Earlier quoted context omitted.

Why would it be sarcastic? The triple bar is also the operator for logical equivalence, which I guess is where the font authors got it.

I assume potential sarcasm would be related to the difficulty differentiating between similar symbols, based on length, with different lexicographic meanings. For example, dash vs endash vs emdash, etc: ‒ – — ― If those symbols were used in a programming language and had different meanings, differentiating quickly could be much more difficult than seeing the difference between -, --, ---, and so on at a glance.

Post by bwidlar » Fri, Jul 21, 2017, 8:57 PM UTC