> To recap, the arguments for single-spacing are: 1. Two-spacing is ugly in proportional fonts. [..] Number 3 is false, because two-spacing gives you two advantages over one-spacing: It looks better in your editor.
I beg to differ. I find that two-spacing feels wrong even in monospace. And even code is not write-only, so it's a stab in my eye every time I 'develop'.
Also, since both HTML and markdown use single-newline chars as word - not paragraph - delimiters, the semantic argument doesn't hold because I'll counter it with [0].
But it wraps at the full width of my terminal (80-some characters per visual line), which is too long.
And it won't display a partial line at the bottom of the screen.
That is, if something wraps to 3 visual lines, but starts on the second row from the bottom,
instead of displaying the first 2 visual lines,
it shows two '@'s.
This prevents me from using the one-sentence-per-line approach nicely.
Any Vim warriors know a solution?
I found as I switched away from the two space style that I was taught in school back to a single space (coincidentally, after reading the referenced Slate article), there was a short period where the single space felt and looked weird.
Nowadays, I use monospace fonts everywhere, and that second space looks downright horrible, and completely extraneous. I feel like the author here countered a fairly well-reasoned article (Slate) with a very subjective point.
Regarding the note on Vim's sentence handling, I'll probably deal with the occasional failure on a word like Mr. rather than having to type out that extra space after every sentence.
Comments
> To recap, the arguments for single-spacing are: 1. Two-spacing is ugly in proportional fonts. [..] Number 3 is false, because two-spacing gives you two advantages over one-spacing: It looks better in your editor.
I beg to differ. I find that two-spacing feels wrong even in monospace. And even code is not write-only, so it's a stab in my eye every time I 'develop'.
Also, since both HTML and markdown use single-newline chars as word - not paragraph - delimiters, the semantic argument doesn't hold because I'll counter it with [0].
[0] http://rhodesmill.org/brandon/2012/one-sentence-per-line/
I would love to use that "one sentence per line" approach, but I can't get lines to soft-wrap in a sane way in Vim. The closest I got was this solution: http://contsys.tumblr.com/post/491802835/vim-soft-word-wrap
But it wraps at the full width of my terminal (80-some characters per visual line), which is too long. And it won't display a partial line at the bottom of the screen. That is, if something wraps to 3 visual lines, but starts on the second row from the bottom, instead of displaying the first 2 visual lines, it shows two '@'s.
This prevents me from using the one-sentence-per-line approach nicely. Any Vim warriors know a solution?
This will tell vim to display "as much as possible of the last line in a window".
I found as I switched away from the two space style that I was taught in school back to a single space (coincidentally, after reading the referenced Slate article), there was a short period where the single space felt and looked weird.
Nowadays, I use monospace fonts everywhere, and that second space looks downright horrible, and completely extraneous. I feel like the author here countered a fairly well-reasoned article (Slate) with a very subjective point.
Regarding the note on Vim's sentence handling, I'll probably deal with the occasional failure on a word like Mr. rather than having to type out that extra space after every sentence.