Re: The less ambiguous math delimiters in tables

[Ihor Radchenko]

Rudolf Adamkovič <rudolf@adamkovic.org> 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. :)

See https://list.orgmode.org/875xwqj4tl.fsf@localhost/

> 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.

Sorry, but no.
Basically, what you propose is a rabbit hole that will introduce new
parser bugs and, worse, new systematic problems with syntax.

For context, I proposed similar ideas to Nicolas, the author of
org-element parser, in the past, and he rejected them firmly.

FYI, my approach to solve this problem is different - I want
(eventually) to allow some kind of alternative syntax for tables that
will allow bypassing similar situations. For example, we can allow
multiple || to serve as delimiters:

|  this |  is |  a     |  normal       |  table  |  row |
|| here || we || allow || verbatim "|" || inside ||    ||

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>