Joplin does not adhere to traditional, commonmark, or even github markdown standards when it comes to how it treats a line ending.
When you use a markdown editor, you are creating in a text editor, not a WYSWYG word processor. It’s markup text. You don’t really know what the end result will be, and the rendering is dynamic anyway. There is a reason a new line is there to make the text more readable, not the rendering. The rendering needs to be algorithmic. Thus, markup text works the way it works… unless you take very specific actions (see next paragraph) a glob of text between two empty lines is a paragraph, and the renderer will figure out how to make it nice in the “published” format.
But sometimes the writer needs to force a hard break. Simple, he or she uses a
<br> or two spaces and a return… or just an extra empty line between paragraphs.
Note: If a person can somehow manage to learn how to do all the other markdown-ish stuff… handling the newline shouldn’t be overly complicated. It just isn’t. And in the end, once you get over the weirdness (it really isn’t, and haven’t you all written any HTML?) it actually makes it easier to work with the editor.
Please, I beg of you, if Joplin is not going to adhere to the standard by default, please at least make how line breaks are handled configurable. It should be as easy as configuring “break: true” and “break: false” somewhere and just flipping that bit. (and I think I found that in…
<sourcecode>/Tools/build-website.js If I understand the code correctly.
Thank you. -t0dd