This line is also a separate paragraph, but. This line is separated from the one above by two newlines, so it will be a *separate paragraph*. Markdown in HTML Does *not* work **very** well. Definition list Is something people use sometimes. You can also use raw HTML in your Markdown, and it'll mostly work pretty well.ĭoes *not* work **very** well. Oh, you can put Markdown into a blockquote. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. This is a very long line that will still be quoted properly when it wraps. Oh, you can *put* **Markdown** into a blockquote.īlockquotes are very handy in email to emulate reply text. > This is a very long line that will still be quoted properly when it wraps. > Blockquotes are very handy in email to emulate reply text. The outer pipes (|) are optional, and you don't need to make the raw Markdown line up prettily.
You can also use inline Markdown.Ĭolons can be used to align columns.
They are an easy way of adding tables to your email - a task that would otherwise require copy-pasting from another application. Tables aren't part of the core Markdown spec, but they are part of GFM and Markdown Here supports them. No language indicated, so no syntax highlighting in Markdown Here (varies on Github). No language indicated, so no syntax highlighting. Var s = "JavaScript syntax highlighting" I recommend only using the fenced code blocks - they're easier and only they support syntax highlighting. Inline `code` has `back-ticks around` it.īlocks of code are either fenced by lines with three back-ticks ```, or are indented with four spaces.
#Humor code snippit how to
Markdown Here supports highlighting for dozens of languages (and not-really-languages, like diffs and HTTP headers) to see the complete list, and how to write the language names, see the highlight.js demo page. However, many renderers - like Github's and Markdown Here - support syntax highlighting. Here's our logo (hover to see the title text):Ĭode blocks are part of the Markdown spec, but syntax highlighting isn't. I'm a relative reference to a repository file Some text to show that the reference links can follow later. Or leave it empty and use the link text itself You can use numbers for reference-style link definitions
Actual numbers don't matter, just that it's a number.Some text that should be aligned with the above item. Actual numbers don't matter, just that it's a number Strong emphasis, aka bold, with asterisks or underscores.Ĭombined emphasis with asterisks and underscores. ~~Scratch this.~~Įmphasis, aka italics, with asterisks or underscores. Strong emphasis, aka bold, with **asterisks** or _underscores_.Ĭombined emphasis with **asterisks and _underscores_**. Table of ContentsĪlternatively, for H1 and H2, an underline-ish style:Īlternatively, for H1 and H2, an underline-ish style: Alt-H1 Alt-H2Įmphasis, aka italics, with *asterisks* or _underscores_.
For more complete info, see John Gruber's original spec. This is intended as a quick reference and showcase.
0 kommentar(er)
