Skip to main content
9 events
when toggle format what by license comment
Aug 15, 2013 at 7:54 comment added slhck Mod @Arjan True, that is the semantically correct way. The problem is that after <pre><code> you'll get an extra line break if you start the code on the next line.
Aug 15, 2013 at 7:52 comment added Arjan Though <pre> (currently) is styled using a fixed-width font, I'd say for code one should use <pre><code>. (Which is exactly what using the four spaces Markdown gets one. Using the four spaces also gets one automatic encoding of HTML entities such as changing <strong> into &lt;strong&gt;.)
Aug 11, 2013 at 14:15 vote accept nixda
Aug 11, 2013 at 13:39 history edited slhckMod CC BY-SA 3.0
added 196 characters in body
Aug 11, 2013 at 13:38 comment added slhck Mod @nixda In cases like the question you linked to it'd probably make sense to use a bulleted list and not use code formatting at all — after all, it's not code or some command here, but just the names of some settings.
Aug 11, 2013 at 13:23 comment added Oliver Salzburg Mod Also, you can indent multi-line code with 4 spaces (Ctrl+K) and wrap inline code in backticks (also Ctrl+K).
Aug 11, 2013 at 13:13 comment added nixda Hm, I stumbled upon this while trying to correct this question. Now, If I replace <code> with <pre> it will add a line break. While this would suit in this case, there are probably cases where I want to avoid line breaks. What then?
Aug 11, 2013 at 13:11 history edited slhckMod CC BY-SA 3.0
added 2 characters in body
Aug 11, 2013 at 13:06 history answered slhckMod CC BY-SA 3.0