this post was submitted on 16 Feb 2024
622 points (100.0% liked)

196

16246 readers
2908 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
greembow@lemmy.blahaj.zone
moss@lemmy.blahaj.zone
moss@lemmy.world
queue@beehaw.org
funky_rodent@lemmy.blahaj.zone
PeachyMcPeachface@lemmy.blahaj.zone
threegnomes@lemmy.blahaj.zone
greembow@lemmy.world
remotelove@lemmy.ca
Roflmasterbigpimp@feddit.de
qaz@lemmy.world
A_Very_Big_Fan@lemm.ee
qaz@lemmy.blahaj.zone
qaz@lemmy.ca
A_Very_Big_Fan@lemmy.world
qaz@lemmy.dbzer0.com
Qaz@lemmy.ml
qaz@sh.itjust.works
qaz@lemmy.sdf.org
622
Rule for Beginners (lemmy.world)
submitted 7 months ago* (last edited 7 months ago) by ThisIsAManWhoKnowsHowToGling@lemmy.dbzer0.com to c/196@lemmy.blahaj.zone
61 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.dbzer0.com/post/14479799

Linux Best Practices

you are viewing a single comment's thread
view the rest of the comments
[โ€“] barsoap@lemm.ee 1 points 7 months ago* (last edited 7 months ago) (1 children)

You're telling markdown to format the code in the language fork() { and then break the code block early by not having > in front of the next line. Here's a quoted code block formatted in sh:

fork() {
   fork | fork &
}
fork
[โ€“] tb_@lemmy.world 1 points 7 months ago

It seems the app I use to browse doesn't play entirely nice with markdown. I updated my formatting a little, thanks for the notice.