Edit File by line

There are some problems one commonly runs into while authoring reST documents:

[500] Fix | Delete

[501] Fix | Delete

* **Separation of inline markup:** As said above, inline markup spans must be

[502] Fix | Delete

separated from the surrounding text by non-word characters, you have to use a

[503] Fix | Delete

backslash-escaped space to get around that. See `the reference

[504] Fix | Delete

<http://docutils.sf.net/docs/ref/rst/restructuredtext.html#inline-markup>`_

[505] Fix | Delete

for the details.

[506] Fix | Delete

[507] Fix | Delete

* **No nested inline markup:** Something like ``*see :func:`foo`*`` is not

[508] Fix | Delete

possible.

[509] Fix | Delete

[510] Fix | Delete

[511] Fix | Delete

.. rubric:: Footnotes

[512] Fix | Delete

[513] Fix | Delete

.. [1] When the default domain contains a :rst:dir:`class` directive, this directive

[514] Fix | Delete

will be shadowed. Therefore, Sphinx re-exports it as :rst:dir:`rst-class`.

[515] Fix | Delete

</textarea></form>

[516] Fix | Delete

[517] Fix | Delete

[518] Fix | Delete

var editor = CodeMirror.fromTextArea(document.getElementById("code"), {

[519] Fix | Delete

lineNumbers: true,

[520] Fix | Delete

});

[521] Fix | Delete

</script>

[522] Fix | Delete

<p>

[523] Fix | Delete

The <code>python</code> mode will be used for highlighting blocks

[524] Fix | Delete

containing Python/IPython terminal sessions: blocks starting with

[525] Fix | Delete

<code>>>></code> (for Python) or <code>In [num]:</code> (for

[526] Fix | Delete

IPython).

[527] Fix | Delete

[528] Fix | Delete

Further, the <code>stex</code> mode will be used for highlighting

[529] Fix | Delete

blocks containing LaTex code.

[530] Fix | Delete

</p>

[531] Fix | Delete

[532] Fix | Delete

<p><strong>MIME types defined:</strong> <code>text/x-rst</code>.</p>

[533] Fix | Delete

</article>

[534] Fix | Delete

[535] Fix | Delete