Back

@bbatsov I have two hot takes here:

• "shell" isn't a language. If it's a bash script, use "bash" so I know not to paste it into my fish shell.

• Lose the dollar sign. This is a code block, and the dollar sign isn't part of the code. Especially relevant for code I'm likely to be pasting into my terminal. Also likely to confuse learners who are unaware of what it's supposed to represent.

@bodil Fair points, but there's also the counter-argument that the $ makes it obvious that something is a command one needs to enter in some shell. (if they are familiar with shells) I'm guessing that why so many people put them in their snippets.

@bbatsov I think so many people put them in their snippets just because they see others doing it, tbh.

@bodil @bbatsov I follow Bodil's way for standalone commands, and as `console` with prompt for examples that include both input and output. I also don't love the latter. I haven't found markup that visually keeps input with output together, while keeping input trivially copiable.

@weavejester @bodil I’m pretty sure that “console” is the way to go when there’s actual output.

@hiredman @bodil First time I hear of this, but I guess it certainly solves that particular problem. :D