Steve's point about vim is the first rational argument I've heard for using two spaces. Saying two spaces looks better with monospaced fonts is an opinion, one which I don't share. But I can buy into two spaces being semantic to your text editor.
I used to use two spaces before the web because that's how I learned it. Way back when I realized that browsers collapse consecutive spaces into one I stopped using them. This argument makes me rethink my position. It also reminds me that I really need to learn more of vim's shortcuts.
In the UK, we were not taught to use two spaces after a full stop, but as my text files are for me only, they are fed through a formatting program before sharing, I may try this.
Use of 'semantic line feeds' obviates the issue. See
Comments
Steve's point about vim is the first rational argument I've heard for using two spaces. Saying two spaces looks better with monospaced fonts is an opinion, one which I don't share. But I can buy into two spaces being semantic to your text editor.
I used to use two spaces before the web because that's how I learned it. Way back when I realized that browsers collapse consecutive spaces into one I stopped using them. This argument makes me rethink my position. It also reminds me that I really need to learn more of vim's shortcuts.
Yup, I noticed that as well.
In the UK, we were not taught to use two spaces after a full stop, but as my text files are for me only, they are fed through a formatting program before sharing, I may try this.
Use of 'semantic line feeds' obviates the issue. See
http://news.ycombinator.com/item?id=4642395
Random information: the Bash formatting utility follows the two spaces convention. The 'par' program uses one space. On Ubuntu...
or The latter produces justified monospace text for that retro look.