However, something breaks (see below without the \\) and we get :
<li>
<code>
line1=\\=line2
</code>
</li>
The \\ not only does not insert a newline, but seems to break the parsing. The same example without them :
- =line1=
=line2=
Correctly parses two distinct code blocks (which will be rendered on same line) :
<li>
<code>line1</code>
<code>line2</code>
</li>
EDIT: Adding a space before the \\ solves the issue (a newline is inserted, and there is no parsing issue). I am unclear about what org-mode says here. I can live with that and add spaces; but, to be sure, I could ask an org-mode maintainer if =foo=\\ is the same as =foo= \\ if you want.
Org documentation states : "If you need to enforce a line break within a paragraph, use ‘\\’ at the end of a line.".
For example :
Should be rendered as something like (as rendered on
github
) :However, something breaks (see below without the
\\
) and we get :The
\\
not only does not insert a newline, but seems to break the parsing. The same example without them :Correctly parses two distinct code blocks (which will be rendered on same line) :
EDIT: Adding a space before the
\\
solves the issue (a newline is inserted, and there is no parsing issue). I am unclear about what org-mode says here. I can live with that and add spaces; but, to be sure, I could ask an org-mode maintainer if=foo=\\
is the same as=foo= \\
if you want.