==============
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.
================
You have given me power that I should not have.
⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠿⠿⠿⠿⠿⠿⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⠟⣉⡥⠶⢶⣿⣿⣿⣿⣷⣆⠉⠛⠿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⡿⢡⡞⠁⠀⠀⠤⠈⠿⠿⠿⠿⣿⠀⢻⣦⡈⠻⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⡇⠘⡁⠀⢀⣀⣀⣀⣈⣁⣐⡒⠢⢤⡈⠛⢿⡄⠻⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⡇⠀⢀⣼⣿⣿⣿⣿⣿⣿⣿⣿⣶⣄⠉⠐⠄⡈⢀⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⠇⢠⣿⣿⣿⣿⡿⢿⣿⣿⣿⠁⢈⣿⡄⠀⢀⣀⠸⣿⣿⣿⣿ ⣿⣿⣿⣿⡿⠟⣡⣶⣶⣬⣭⣥⣴⠀⣾⣿⣿⣿⣶⣾⣿⣧⠀⣼⣿⣷⣌⡻⢿⣿ ⣿⣿⠟⣋⣴⣾⣿⣿⣿⣿⣿⣿⣿⡇⢿⣿⣿⣿⣿⣿⣿⡿⢸⣿⣿⣿⣿⣷⠄⢻ ⡏⠰⢾⣿⣿⣿⣿⣿⣿⣿⣿⣿⡿⠟⢂⣭⣿⣿⣿⣿⣿⠇⠘⠛⠛⢉⣉⣠⣴⣾ ⣿⣷⣦⣬⣍⣉⣉⣛⣛⣉⠉⣤⣶⣾⣿⣿⣿⣿⣿⣿⡿⢰⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣧⡘⣿⣿⣿⣿⣿⣿⣿⣿⡇⣼⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣇⢸⣿⣿⣿⣿⣿⣿⣿⠁⣿⣿⣿⣿⣿⣿⣿⣿⣿
\⣿⣿⣿⣿⣿⣿⠿⢋⣥⣴⣶⣶⣶⣬⣙⠻⠟⣋⣭⣭⣭⣭⡙⠻⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⡿⢋⣴⣿⣿⠿⢟⣛⣛⣛⠿⢷⡹⣿⣿⣿⣿⣿⣿⣆⠹⣿⣿⣿⣿ ⣿⣿⣿⡿⢁⣾⣿⣿⣴⣿⣿⣿⣿⠿⠿⠷⠥⠱⣶⣶⣶⣶⡶⠮⠤⣌⡙⢿⣿ ⣿⡿⢛⡁⣾⣿⣿⣿⡿⢟⡫⢕⣪⡭⠥⢭⣭⣉⡂⣉⡒⣤⡭⡉⠩⣥⣰⠂⠹ ⡟⢠⣿⣱⣿⣿⣿⣏⣛⢲⣾⣿⠃⠄⠐⠈⣿⣿⣿⣿⣿⣿⠄⠁⠃⢸⣿⣿⡧ ⢠⣿⣿⣿⣿⣿⣿⣿⣿⣇⣊⠙⠳⠤⠤⠾⣟⠛⠍⣹⣛⣛⣢⣀⣠⣛⡯⢉⣰ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⡶⠶⢒⣠⣼⣿⣿⣛⠻⠛⢛⣛⠉⣴⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⡿⢛⡛⢿⣿⣿⣶⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⡈⢿⣿ ⣿⣿⣿⣿⣿⣿⣿⠸⣿⡻⢷⣍⣛⠻⠿⠿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠿⢇⡘⣿ ⣿⣿⣿⣿⣿⣿⣿⣷⣝⠻⠶⣬⣍⣛⣛⠓⠶⠶⠶⠤⠬⠭⠤⠶⠶⠞⠛⣡⣿ ⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⣶⣬⣭⣍⣙⣛⣛⣛⠛⠛⠛⠿⠿⠿⠛⣠⣿⣿ ⣦⣈⠉⢛⠻⠿⠿⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡿⠿⠛⣁⣴⣾⣿⣿⣿⣿ ⣿⣿⣿⣶⣮⣭⣁⣒⣒⣒⠂⠠⠬⠭⠭⠭⢀⣀⣠⣄⡘⠿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣦⡈⢿⣿⣿⣿⣿⣿
\──────▄▌▐▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▌
───▄▄██▌█ BEEP BEEP
▄▄▄▌▐██▌█ -15LP DELIVERY
███████▌█▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▌
▀(⊙)▀▀▀▀▀▀▀(⊙)(⊙)▀▀▀▀▀▀▀▀▀▀(⊙)\
\He he he he I’m gonna draw dicks everywhere he he he he he⠀⠀⠀⠀⠀⠀
Doing the Lord’s work
Still works better when encased with code block stuff,
```
You can also put a backslash before a newline, like this
Line1\ Line2\ Line3Looks like this:
Line1
Line2
Line3Without the backslashes: Line1 Line2 Line3
With two newlines:
Line1
Line2
Line3
Also check out this Markdown tutorial , it’s very helpful.
Discovered this as well the other day. Much better for me, since you can see it, and also 2 spacebar hits on mobile makes a full-stop/period for me.
Same, I actually do three spaces if you count the full-stop. (I didn’t count it)
This does not seem to render as intended in Sync. It’s like the opposite effect. The backslashes are showing in the comments, but invisible in the code blocks lol.
ITT people realising what markdown is.
One time on Reddit there was a whole thread dedicated to how awful and arbitrary and stupid the “undocumented” comment feature was.
I just linked the markdown docs and got downvoted to hell because “reading the manual is unintuitive”
Comments truly did kill that platform
M.A.G.I.C
Markdown’s
Actually
Good
In
Comments#IKR
Reddit was like that too.
Because the line break in markdown is two spaces.
Markdown is pretty great to work with.
This assumes your Lemmy client uses a good markdown library.
Yes, this assumes you’re using a good Lemmy client
This assumes you’re using a client.
Look behind you.OH YOUR GOD!
NO!
THE HORROR!
How often do you get to use this awesome picture? =D
Imagine needing a client, real lemmings use the API directly with cURL
What colour are your programmer socks
I don’t have any TwT
Might buy them at some point to gain a 200% programming boost, and of course paired with a skirt.
A simple search for lemmy markdown would tell you all the different textual options for a clean Lemmy comment/post
This is standard markdown behavior. It was like this on reddit and many other places, too.
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
I didn’t know this, and I found it super helpful!
I also didn’t know about backslashes
I just used double carriage returns like a wild savage!Thanks very much :)
Oh
My
God
This is awesometest
testtest
FUCK YEAAAAAHHH
Ok this was awesome. I wondered what I was doing wrong.
I always defaulted to a bullet list.
No moreYou can also add a \ to the end
of the lines and have only single spaced
line breaksThough I think they may break in one of the mobile apps with a funky markdown interpreter.
Edit: For clarity, here’s the same lines in a codeblock
You can also add a \ to the end\ of the lines and have only single spaced\ line breaksWell, I think
That changes How I write some stuffedit: the 2 white spaces didn’t work
edit2: the white spaces have to be on the PREVIOUS line, not “behind”, which I thought meant “start the line with 2 spaces”I edited my original to clarify. Thanks!
Cool discovery.
This post is a good resource for other Lemmy formatting tips and tricks.
I recently discovered that Lemmy’s desktop site shortens groups of more than 3 exclamation points and groups of more than 3 question marks in a row down to only 3, and that pairs of periods will be rounded up into an ellipses.
I’d like to see a community to help document all of the obscure formatting tricks and quirks for Lemmy.
Edit: You can apparently circumvent Markdown formatting by putting a backslash \ in front of the command to format. For example, if you wanted to start a line with the greater than symbol >, you can put the backslash \ in front of the greater than sign > to prevent the text from being formatted as a quote
Hey I posted this super secret hack yesterday or the day before here on Lemmers in a comment.
