Ihor Radchenko writes: > Juan Manuel Macías <maciasch...@posteo.net> writes: > >>> Paragraph\\ >>> @@latex:[foo]@@ >> >> But since in both cases it is literal LaTeX code, the correct thing >> would be for the user to be in charge of adding the curly braces to the >> square brackets. I mean in such scenario it is LaTeX code, not Org. > > Not really. Because we do not give guarantees about the details of LaTeX > export, we should try hard to not break things that users may put into > literal export snippets. > >> Anyway, in both examples it does not make sense for LaTeX to end a >> paragraph with the \\ macro, which is why we commented in previous >> messages in the thread. The \\ macro is only used in horizontal mode; >> this macro does not add a new paragraph but rather a forced line break >> within the paragraph. > > In the example with @@latex:[foo]@@, \\ is not at the end of a paragraph > - it is inside paragraph.
What I mean is that literal LaTeX code is LaTeX code, despite the redundancy. IMHO, Org's only duty in that case is to export such literal code as valid LaTeX code, but Org "does not know" what that literal code consists of. The user who enters the literal LaTeX code is the one who has the duty to add the necessary elements to that code so that it is compiled correctly by LaTeX. Let's look at this as a territorial question: Scenario A: @@LaTeX:\libebreak@@ [ipsum] ==> the problem is in Org territory Scenario B: lorem\\ @@latex:[ipsum]@@ ==> the problem is in the user's territory Best regards, Juan Manuel
