4 ms·
Two big reasons for continuing to use monospaced fonts in programming: 1) Support for vim navigation, where hjkl move you one character in a direction on an ev
by joshjb17 4y ago
Two big reasons for continuing to use monospaced fonts in programming:
1) Support for vim navigation, where hjkl move you one character in a direction on an evenly spaced grid. Remove that uniform spacing and up ceases to be “up”
2) Legibility for formatted comments and ASCII art (could argue these should be avoided but I’ve seen some magical ASCII art in code)
////////////////
// My Comment //
////////////////
- WastingMyTime89 4y agoI both use vim movement and a proportional font for coding. 1/ That’s already broken by line wrapping. gj is the command moving up in the grid not j. The fact you are confusing the two should tell you how little of a difference some sideway movement makes. 2/ Don’t use ASCII art in code. It’s annoying for people not using monospaced font and I’m not alone.
- adrusi 4y agoMany people map j/k to gj/gk and forget that's not the default behavior.
- joshjb17 4y agoInteresting, wasn’t aware of gj. I’ve always worked in code bases where a 120 or less character width is imposed, removing the possibility of line wrapping. TIL, mapping j to gj sounds like a good move.