Ihor Radchenko <yanta...@posteo.net> writes:
> In a theoretical case if we agree to what you are suggesting, it should
> not be just for tables. There are similar cases with other markup, like
>
> *foo =* *= bar*
Agreed! We could introduce a kind of escaping that means "this MUST be
interpreted as markup" and/or "this MUST NOT be interpreted as markup",
but that could lead to documents that are hard to read for humans. Or,
we could add structured markup that is unambiguous and takes precedence
over all unstructured markup. For example:
emphasis{...}
verbatim{...}
table[...]{...}
src[...]{...}
The last one already exists. :)
That said, as for my original problem, I still think that \(...\) should
take precedence over |. Even if we added structured latex{...} markup,
it should not be necessary in my case, as Org should not severely break
basic LaTeX within tables in the first place.
Rudy
--
"All you have to do is write one true sentence. Write the truest
sentence that you know." --- Ernest Miller Hemingway (1899-1961)
Rudolf Adamkovič <rud...@adamkovic.org> [he/him]
http://adamkovic.org
