Is this why HN joins consecutive lines? This is on line 2. And this is on line 4.
No, that's just how markdown works, and HN uses markdown.
Writing one sentence per line
31–40 of 307 posts
Re: Writing one sentence per line
#32I approach this by separating writing from editing. Just keep writing, ignore the typos, self-censorship or formatting and keep moving. So, I've build myself an app to make that easier. Essentially, it's just a more stupid version of a text box. It's free, it's private, and it's meant to put you in the state of flow. I've been using it every day for the past 3 years or so and I know that some people find it useful to…
>I approach this by separating writing from editing. Just keep writing, ignore the typos, self-censorship or formatting and keep moving. You've (re)discovered the old adage: write drunk, edit sober.
Close but, no cigar. Code sober, debug drunk!
Re: Writing one sentence per line
#33Or, with a bit more nuance: Semantic line breaks https://sembr.org/
> 5. A semantic line break SHOULD occur after an independent clause as punctuated by a comma (,), semicolon (;), colon (:), or em dash (—).
Uh oh, that’s incompatible with standard em dash usage, which is with no surrounding whitespace.
(I’m designing a lightweight markup language of my own, and it’s tempting to special-case an em dash at the end of a line that is not preceded by a space, to join to the next line without inserting a space, but I’ve been trying to avoid nuance in rules. But I definitely do want to put line breaks after em dashes sometimes.)
Re: Writing one sentence per line
#34Reading this makes me think it might be generally beneficial to finally convey the semantics of sentence boundaries to the resulting output as well, like some `
Sentence #1. Sentence #2.` wrappers: it would introduce possibility (for author or user) to break it into lines again or apply any other styling, and might improve interaction (think: select single sentence), or some further processing or contextual styling (think "make all single-sentence paragraphs stand out".)
Strange there is no truly "semantic" way to mark-up sub-paragraph chunk of text in HTML; all 'inline' tags are intended for "words" or for including several sentences at once (like emphasis, quote, code, sample, mark, etc.). I have some murky memory I've read some discussion explaining that the concept of "sentence" is quite problematic and in no way universal, but cannot dig it up now.
(This comment started as But how are we supposed to sneak our beloved double spaces between sentences in the output now? semi-pun, but after all, this post-processing idea answers it.)
Re: Writing one sentence per line
#35I approach this by separating writing from editing. Just keep writing, ignore the typos, self-censorship or formatting and keep moving. So, I've build myself an app to make that easier. Essentially, it's just a more stupid version of a text box. It's free, it's private, and it's meant to put you in the state of flow. I've been using it every day for the past 3 years or so and I know that some people find it useful to…
Similar idea I made a few years ago. A text editor with no editing allowed and lets you export to Word/MD/HTML for later editing https://first-draft.netlify.app
Sweet! If you don't mind sharing, did anyone donate through ko-fi?
I think there's still potential in writing tools with decent UX (iA Writer and such) and I know that some people wanted to pay me for Enso, so I'm trying to figure out the best course of action: either charge premium for a premium native app or let the people chip in. Paid products tend to get more valuable feedback.
Re: Writing one sentence per line
#36I completely agree.
Using one line per sentence (and soemtime more lines when the sentence is longer)
makes it way easier to structure the text.
Markdown and are perfectly able to fit the text to the device you are reading on.
It also makes version control and diffs more usable.
However, I can also agree that this style might be not suitable for non-technical writing.
Re: Writing one sentence per line
#37Earlier quoted context omitted.
>I approach this by separating writing from editing. Just keep writing, ignore the typos, self-censorship or formatting and keep moving. You've (re)discovered the old adage: write drunk, edit sober.
Close but, no cigar. Code sober, debug drunk! https://sonnet.io/posts/code-sober-debug-drunk/
[deleted]
Re: Writing one sentence per line
#38Or, with a bit more nuance: Semantic line breaks https://sembr.org/
Looks good - but I do not agree with
> 3. A semantic line break SHOULD NOT alter the intended meaning of the text.
That should be #1 MUST NOT
Re: Writing one sentence per line
#39This is my sentence.
There are many like it, but this one is mine.
Re: Writing one sentence per line
#40Earlier quoted context omitted.
>I approach this by separating writing from editing. Just keep writing, ignore the typos, self-censorship or formatting and keep moving. You've (re)discovered the old adage: write drunk, edit sober.
Close but, no cigar. Code sober, debug drunk! https://sonnet.io/posts/code-sober-debug-drunk/
[deleted]