mirror of
https://github.com/vale981/emacs-ipython-notebook
synced 2025-03-12 04:36:38 -04:00
b431f57ce1
git-subtree-dir: lib/markdown-mode git-subtree-split: 3f11a4a7609ba2a507ee10f491bdadab28e9b985
30 lines
960 B
Text
30 lines
960 B
Text
This is *italic.*
|
|
This is **bold.**
|
|
This is `code`.
|
|
This is ``code`containing`backticks``.
|
|
|
|
Seven backquotes in a row ``````` do not constitute a code span.
|
|
|
|
If backquotes begin or end a code span, you have to use spaces,
|
|
like `` `this` ``. Markdown removes any leading and trailing
|
|
whitespace. Only the space a the end is necessary,
|
|
like ```this` ``.
|
|
|
|
A backslash as the final character in an inline code fragment does
|
|
*not* escape the backquote. That is, `C-h C-\` will render as
|
|
|
|
<code>C-h C-\</code>
|
|
|
|
However, we can escape what would otherwise be a leading backquote,
|
|
as in \`foo\` or \`bar\`.
|
|
|
|
But this will be a code span crossing lines: \`foo` or
|
|
bar ` containing only "or bar".
|
|
|
|
This should result in three backquotes in a code span `` ``` `` and
|
|
they should even match across across lines `` ```
|
|
``, like so. However, backquotes should not `` ``` match
|
|
|
|
across two blocks``.
|
|
|
|
Links have several components: [text](http://www.w3.org/ "title").
|