Timeline for How can I quickly and easily format my code for SE sites' posts?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 23, 2015 at 19:08 | history | edited | Eliah Kagan | CC BY-SA 3.0 |
removed spurious / that made the opening <code> tag an ending tag (besides that typo, this looks good to me)
|
| Apr 23, 2015 at 19:06 | comment | added | Byte Commander Mod | @EliahKagan Edited again. Do you agree now? :) | |
| Apr 23, 2015 at 19:06 | history | edited | Byte CommanderMod | CC BY-SA 3.0 |
added 115 characters in body
|
| Apr 23, 2015 at 18:40 | comment | added | Eliah Kagan |
Thanks. Bit there's a problem related to an apparent difference in the way SE renders <pre> with and without <code>. The newline between <pre><code> and the code is rendered as a blank line of code. So <pre><code> should be at the start of the fist line of code. And while it doesn't currently seem necessary (in my browser, etc.), it's probably best for </code></pre> to be at the end of the last line as well, rather than on its own line. <pre> </pre> by themselves appear to avoid this requirement, but I wouldn't recommend it for that--I don't think that behavior can be relied on.
|
|
| Apr 23, 2015 at 18:32 | comment | added | Byte Commander Mod | @EliahKagan I edit my answer and included your advice. Thank you! | |
| Apr 23, 2015 at 18:31 | history | edited | Byte CommanderMod | CC BY-SA 3.0 |
added 155 characters in body
|
| Apr 23, 2015 at 18:19 | comment | added | Eliah Kagan |
For writing explicit HTML for a block of code, I suggest <pre><code> </code></pre> rather than just <pre> </pre>. Indenting with four spaces (which is what Ctrl+K/{} does) causes the site to produce <pre><code> </code></pre> markup. For the site's current CSS on current popular browsers configured in the usual way, the difference appears small to nonexistent. But I think future site changes, custom style sheets (such as for accessibility), other browsers, and some techniques used to read posts in SE data dumps might differently with and without the nested <code> </code> tags.
|
|
| Apr 23, 2015 at 17:16 | comment | added | Byte Commander Mod | No, I don't. I also have to admit I never had to convert tabs yet... | |
| Apr 23, 2015 at 16:44 | comment | added | kos | That is useful, but I really can't stand the TAB thing. I usually indent with tabs, and sometimes i write long scripts. I don't think there's a way to enter / convert TAB characters within the editor, or maybe you know something? | |
| Apr 23, 2015 at 16:42 | comment | added | muru |
Using HTML tags too much defeats the purpose of Markdown, the simplicity and readability that it provides. They should be used sparingly - <kbd> tags being an example.
|
|
| Apr 23, 2015 at 16:32 | history | answered | Byte CommanderMod | CC BY-SA 3.0 |