3 ms·
Interesting take. On hackernews I also learned about an approach called "ventilated prose" or writing with "semantic line breaks." That is, when you write, say
by supersrdjan 5y ago
Interesting take. On hackernews I also learned about an approach called "ventilated prose" or writing with "semantic line breaks." That is, when you write, say in vim or emacs, you put one clause per line. Then when you are done, you can use pandoc or something similar to convert what you wrote into standard prose. But the artificial line breaks, which results in thin lines, make it easier to edit, and also easier to comprehend diffs if you use git to track changes.
- siscia 5y agoI find the line break to be semantical important! So it is different if there is or if there is not a line break. How do you manage it? Double line break?
- supersrdjan 5y agoPandoc ignores single line breaks when exporting markdown. So all of this would be treated as a single sentence. But an empty space in between indicates a new paragraph. If for some reason you require to have separate lines, perhaps when enumerating something, you can leave two trailing spaces after the line, that preserves the break.
- supersrdjan 5y agoOh, even hackernews ignores single line breaks. I wrote this coment like this: ``` Pandoc ignores single line breaks when exporting pandoc. So all of this would be treated as a single sentence [sic, I wanted to write "line"]. ```
- supersrdjan 5y agohuh... sorry, I don't know how to use hacker news to show you what I mean... it keeps squishing my lines.
- telotortium 5y agoInstead of leaving two trailing spaces, I tend to just use `<br>`, which is more explicit.