==============
This is a first line This is a second line This is the third line.
==============
These all appear on the same line eventhough I wrote them on separate lines
If I add a “enter” after each line, they’ll appear on separate lines, but have white spaces in between.
==============
This is the first line
This is the second line
This is the third line.
===============
Now I only add two spaces behind each line and they’ll appear just as I wrote them
================
This is the first line.
This is the second line.
This is the third line.
================
One of the things I don’t like about markdown. Carriage returns are just built into most languages now. I shouldn’t have to use double spaces (which put auto periods in on iOS and Android) or a slash to get the same effect. That’s counterintuitive.
It’s a feature. The / means you can write your lines as long as you editor Windows is, but when someone rendering it as rtf they cannot just wrapper it any way they want. Doesn’t matter if they’re reading it in portrait view or landscape
I think word wrapping is automatically assumed is the default. I’m not aware of any rtf editors that don’t display wrapped as the default.
I wrote out a whole massive reply that ended with ‘and there’s no real reason to break this…’ and then I thought… But really? Actually there are so many form factors in which you can view Lemmy that ‘pre-rendering’ the line breaks makes basically no sense, and I can’t think of many tools or typing habits that would otherwise introduce them