# Formatting Sand-Box

As per the SO question here (if you want to know how they did something there, take a look at the source, as per the hack documented here), I suggest that this (CW) question be used for testing purposes. Feel free to edit this question, add answers, experiment with deletion or markdown or what-have you.

Use this Markdown Editing Help reference as a guide, or this tome if you want to know every detail.

I'll take this question down if the community thinks that it is inappropriate, but if it is appropriate, we could have something like it pointed to in the FAQ and in the markdown manual.

• Not a duplicate of this LaTeX sandbox proposal – Kevin Vermeer Jul 30 '10 at 19:53
• See this page for information on comment markup. – Kevin Vermeer Jul 30 '10 at 19:59
• Has nothing to do with LaTeX sandbox porposal...but if this is confusing I'll edit to make it clear. – Yossi Farjoun Jul 31 '10 at 1:17
• Testing backslashes in comments: \ ~ <bt><bt>\<bt><bt>; \\ ~ <bt>bt>\\<bt><bt>; \  ~ <bt><bt>\ <bt><bt>. Here <bt>=. – Werner Jan 3 '13 at 0:31
• @Werner -- i think one of those bracketed bts has a left angle missing. (thanks for the pointer.) – barbara beeton Mar 26 '13 at 19:31

Here's an answer which can be used as sandbox answer. Feel free to edit if you wish to try markdown. Below the line would be good. So, the question doesn't remain unanswered.

Here's a funny formatting trap: code after a list item doesn't format: Why do code snippets not work after lists? The solution is to insert an HTML comment between the list item and the code:

• A list item

\begin{document}

• Another list item with <!> after it and some following code: (needs to be separated by blank lines):

\begin{document}


Perl?

sub run_command (@) {
my $origcmdline = join(" ", grep {defined} @_); return if$origcmdline eq "";

my $cmdline =$origcmdline;


description lists

\predisplaypenalty
penalty for page break just before a display

doesn't look very promising in preview…

TEX

Hm, would've been nice

• A list
•   Some code


(See LaTeX Editors/IDEs.)

Bla bla bla*.*
Bla bla bla_._
Bla bla bla.

The text is from http://el.wikipedia.org/wiki/Αθήνα foo

• @morbusg: Interesting, description lists should work according to meta.stackexchange.com/questions/1777/…. – doncherry Apr 9 '12 at 12:50
• @doncherry They do, at least the HTML tags show up in the source code. However, as there is no CSS to format them, the result is not very pretty. See also the feature request Better style for HTML 'definition list' <dl> elements on meta.SO. – diabonas Apr 9 '12 at 13:34
• <code>\\</code> – Canageek Jul 31 '12 at 22:58
• \, \\... – Bruno Le Floch Aug 1 '12 at 7:30
• With this setup, does the font for regular text come from the charter package or mathdesign? Switching the order of \usepackage{charter} and \usepackage[charter]{mathdesign} produces different outputs. Also, the latter setup complains about Font shape T1/bch/m/fsc undefined(Font) .. (small caps?) – DCh Apr 10 '14 at 17:15

Typesetting backslashes, backticks and spaces:

1.
2. \
3. \
4. \\
5. \ 
6.
7. 
8. 
9.  
10. 
11. 
12. \
13. \
14. 

Use HTML formatting mixed with markdown for spaces.

1. &nbsp;
2. \\
3. \
4. \\
5. <code>\&nbsp;</code>
6. 
7. 
8. <code></code>
9.  
10. <code></code>
11.  
12. <code>\\</code>
13. \ 
14. <code>&nbsp;</code>


Here are the rules for inline code in posts and comments.

POSTS: If you want backticks inside an inline code snippet, surround them with any amount of backticks not used in the code. Examples:

• this is a backtick thing renders as this is a backtick thing
• here are one  two  three  backticks renders as here are one  two  three  backticks
• Use spaces if backticks are at beginning or end -  $  renders as $
• testing testing\123testing renders as testing testing\123testing

COMMENTS: Simply use \ to escape backticks. Limitation: you can't escape backslashes, so you can't have a backslash at the end of an inline code snippet. Also, test123test doesn't work.

• this is a \backtick\ thing renders as this is a backtick thing
• etc.
• testing testing\ 123 testing renders as testing testing\ 123 testing
• [meta]: [meta]; [main]: TeX - LaTeX; [about]: tour; [help]: help center – Speravir Jan 28 '14 at 20:52
• [About TeX-LaTeX Stack Exchange][about]: [About TeX-LaTeX Stack Exchange]tour – Speravir Jan 28 '14 at 20:59
• [meta.tex.se]: TeX - LaTeX Meta; [tex.se]: TeX - LaTeX – Werner Sep 12 '14 at 5:47

Just testing some entities:

&#211hello; in the preview produces Óhello; What happens in the main?

&#211hello;

Strike out works.

Shrt nswrs r k.​​​

• cmmnt. – yo' Jan 13 '13 at 21:07

Trying to see if I can put in < and >:

$1 > 2$ while $2 < 3$.  \\
Seems to be OK with new stuff.


Code inside list is indented by more space (twice more than the usual):

Code:

This is code because four spaces go before me.

• This is a bullet!

I am not code even though there are four spaces before me. But, if eight spaces precede me, I'll be one.

Like this.

1. a list
1. with stuff
2. in it

Testing link prettification for https URLs: Formatting Sand-Box

Testing link prettification for http` URLs: Formatting Sand-Box

Testing link prettification for protocol-less URLs: //meta.tex.stackexchange.com/q/208/21344