aboutsummaryrefslogtreecommitdiff
path: root/imports/codemirror/mode/rst
diff options
context:
space:
mode:
authorPushkar Joshi2012-02-24 12:08:49 -0800
committerPushkar Joshi2012-02-24 12:08:49 -0800
commit03ca7a5ed13c25faaa9100bb666e062fd15335e6 (patch)
treec51112223ceb9121cd595a60335eb2795215590f /imports/codemirror/mode/rst
parentfcb12cc09eb3cd3b42bd215877ba18f449275b75 (diff)
parent053fc63a2950c7a5ee4ebf98033b64d474a3c46e (diff)
downloadninja-03ca7a5ed13c25faaa9100bb666e062fd15335e6.tar.gz
Merge branch 'pentool' into brushtool
Conflicts: imports/codemirror/mode/scheme/scheme.js js/tools/BrushTool.js
Diffstat (limited to 'imports/codemirror/mode/rst')
-rwxr-xr-ximports/codemirror/mode/rst/index.html525
-rwxr-xr-ximports/codemirror/mode/rst/rst.js326
2 files changed, 851 insertions, 0 deletions
diff --git a/imports/codemirror/mode/rst/index.html b/imports/codemirror/mode/rst/index.html
new file mode 100755
index 00000000..fd75a284
--- /dev/null
+++ b/imports/codemirror/mode/rst/index.html
@@ -0,0 +1,525 @@
1<!doctype html>
2<html>
3 <head>
4 <title>CodeMirror: reStructuredText mode</title>
5 <link rel="stylesheet" href="../../lib/codemirror.css">
6 <script src="../../lib/codemirror.js"></script>
7 <script src="rst.js"></script>
8 <style type="text/css">.CodeMirror {border-top: 1px solid black; border-bottom: 1px solid black;}</style>
9 <link rel="stylesheet" href="../../doc/docs.css">
10 </head>
11 <body>
12 <h1>CodeMirror: reStructuredText mode</h1>
13
14<form><textarea id="code" name="code">
15.. This is an excerpt from Sphinx documentation: http://sphinx.pocoo.org/_sources/rest.txt
16
17.. highlightlang:: rest
18
19.. _rst-primer:
20
21reStructuredText Primer
22=======================
23
24This section is a brief introduction to reStructuredText (reST) concepts and
25syntax, intended to provide authors with enough information to author documents
26productively. Since reST was designed to be a simple, unobtrusive markup
27language, this will not take too long.
28
29.. seealso::
30
31 The authoritative `reStructuredText User Documentation
32 &lt;http://docutils.sourceforge.net/rst.html&gt;`_. The "ref" links in this
33 document link to the description of the individual constructs in the reST
34 reference.
35
36
37Paragraphs
38----------
39
40The paragraph (:duref:`ref &lt;paragraphs&gt;`) is the most basic block in a reST
41document. Paragraphs are simply chunks of text separated by one or more blank
42lines. As in Python, indentation is significant in reST, so all lines of the
43same paragraph must be left-aligned to the same level of indentation.
44
45
46.. _inlinemarkup:
47
48Inline markup
49-------------
50
51The standard reST inline markup is quite simple: use
52
53* one asterisk: ``*text*`` for emphasis (italics),
54* two asterisks: ``**text**`` for strong emphasis (boldface), and
55* backquotes: ````text```` for code samples.
56
57If asterisks or backquotes appear in running text and could be confused with
58inline markup delimiters, they have to be escaped with a backslash.
59
60Be aware of some restrictions of this markup:
61
62* it may not be nested,
63* content may not start or end with whitespace: ``* text*`` is wrong,
64* it must be separated from surrounding text by non-word characters. Use a
65 backslash escaped space to work around that: ``thisis\ *one*\ word``.
66
67These restrictions may be lifted in future versions of the docutils.
68
69reST also allows for custom "interpreted text roles"', which signify that the
70enclosed text should be interpreted in a specific way. Sphinx uses this to
71provide semantic markup and cross-referencing of identifiers, as described in
72the appropriate section. The general syntax is ``:rolename:`content```.
73
74Standard reST provides the following roles:
75
76* :durole:`emphasis` -- alternate spelling for ``*emphasis*``
77* :durole:`strong` -- alternate spelling for ``**strong**``
78* :durole:`literal` -- alternate spelling for ````literal````
79* :durole:`subscript` -- subscript text
80* :durole:`superscript` -- superscript text
81* :durole:`title-reference` -- for titles of books, periodicals, and other
82 materials
83
84See :ref:`inline-markup` for roles added by Sphinx.
85
86
87Lists and Quote-like blocks
88---------------------------
89
90List markup (:duref:`ref &lt;bullet-lists&gt;`) is natural: just place an asterisk at
91the start of a paragraph and indent properly. The same goes for numbered lists;
92they can also be autonumbered using a ``#`` sign::
93
94 * This is a bulleted list.
95 * It has two items, the second
96 item uses two lines.
97
98 1. This is a numbered list.
99 2. It has two items too.
100
101 #. This is a numbered list.
102 #. It has two items too.
103
104
105Nested lists are possible, but be aware that they must be separated from the
106parent list items by blank lines::
107
108 * this is
109 * a list
110
111 * with a nested list
112 * and some subitems
113
114 * and here the parent list continues
115
116Definition lists (:duref:`ref &lt;definition-lists&gt;`) are created as follows::
117
118 term (up to a line of text)
119 Definition of the term, which must be indented
120
121 and can even consist of multiple paragraphs
122
123 next term
124 Description.
125
126Note that the term cannot have more than one line of text.
127
128Quoted paragraphs (:duref:`ref &lt;block-quotes&gt;`) are created by just indenting
129them more than the surrounding paragraphs.
130
131Line blocks (:duref:`ref &lt;line-blocks&gt;`) are a way of preserving line breaks::
132
133 | These lines are
134 | broken exactly like in
135 | the source file.
136
137There are also several more special blocks available:
138
139* field lists (:duref:`ref &lt;field-lists&gt;`)
140* option lists (:duref:`ref &lt;option-lists&gt;`)
141* quoted literal blocks (:duref:`ref &lt;quoted-literal-blocks&gt;`)
142* doctest blocks (:duref:`ref &lt;doctest-blocks&gt;`)
143
144
145Source Code
146-----------
147
148Literal code blocks (:duref:`ref &lt;literal-blocks&gt;`) are introduced by ending a
149paragraph with the special marker ``::``. The literal block must be indented
150(and, like all paragraphs, separated from the surrounding ones by blank lines)::
151
152 This is a normal text paragraph. The next paragraph is a code sample::
153
154 It is not processed in any way, except
155 that the indentation is removed.
156
157 It can span multiple lines.
158
159 This is a normal text paragraph again.
160
161The handling of the ``::`` marker is smart:
162
163* If it occurs as a paragraph of its own, that paragraph is completely left
164 out of the document.
165* If it is preceded by whitespace, the marker is removed.
166* If it is preceded by non-whitespace, the marker is replaced by a single
167 colon.
168
169That way, the second sentence in the above example's first paragraph would be
170rendered as "The next paragraph is a code sample:".
171
172
173.. _rst-tables:
174
175Tables
176------
177
178Two forms of tables are supported. For *grid tables* (:duref:`ref
179&lt;grid-tables&gt;`), you have to "paint" the cell grid yourself. They look like
180this::
181
182 +------------------------+------------+----------+----------+
183 | Header row, column 1 | Header 2 | Header 3 | Header 4 |
184 | (header rows optional) | | | |
185 +========================+============+==========+==========+
186 | body row 1, column 1 | column 2 | column 3 | column 4 |
187 +------------------------+------------+----------+----------+
188 | body row 2 | ... | ... | |
189 +------------------------+------------+----------+----------+
190
191*Simple tables* (:duref:`ref &lt;simple-tables&gt;`) are easier to write, but
192limited: they must contain more than one row, and the first column cannot
193contain multiple lines. They look like this::
194
195 ===== ===== =======
196 A B A and B
197 ===== ===== =======
198 False False False
199 True False False
200 False True False
201 True True True
202 ===== ===== =======
203
204
205Hyperlinks
206----------
207
208External links
209^^^^^^^^^^^^^^
210
211Use ```Link text &lt;http://example.com/&gt;`_`` for inline web links. If the link
212text should be the web address, you don't need special markup at all, the parser
213finds links and mail addresses in ordinary text.
214
215You can also separate the link and the target definition (:duref:`ref
216&lt;hyperlink-targets&gt;`), like this::
217
218 This is a paragraph that contains `a link`_.
219
220 .. _a link: http://example.com/
221
222
223Internal links
224^^^^^^^^^^^^^^
225