644
GET BOMBADEERED, IDIOT
(mander.xyz)
A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.
Rules
This is a science community. We use the Dawkins definition of meme.
Here's an attempted explanation
I feel like being part of a setup that was created for this comment. That's more than I ever expected. Thank you very much.
Why did you use a code block for a quote?
I didn't do it on purpose, I just copied and pasted
Ah I see, should familiarize yourself with Lemmy’s markdown.
I know it but I haven't seen a good way of doing a long quote. Do I need the > on every single line? I've no idea why this time it put it into a code block, maybe something to do with my app (sync). The comment actually looks fine in a code block on my app so I thought it was good enough. Didn't realise how shit it looked on desktop until you brought it up.
Just gotta do the start of each paragraph.
This is paragraph 3 without the leading
>
Each application will handle markdown differently, I would just stick with what is documented by Lemmy devs.
idk why but I kind of like to read it with random keywords highlighted and every apostrophe toggling the effect
I tend to use them because they're easier than quotes.
Newlines won't terminate the block but with quotes you have to manually insert a
>
at each linebreak.I understand you can use double space to use a markdown linebreak and mitigate the need to do it.
However if you're copy pasting a quote this still has to be done manually by the person copying the text.
In which case manually putting the
>
on empty lines is easier but still more time consuming than using a code block.This is for all flavors of markdown I've used including github flavored.