Rudolf Adamkovič <rud...@adamkovic.org> writes: >> It is not just about \(...\). > > Of course, and I agree that a more general mechanism is needed to solve > all precedence problems, be it in tables, or (better) in general. But, > as I said before, even if we had such a mechanism, it should not be > necessary to use it for \(...\) in tables, as there is no ambiguity, and > so no "madness", no? Does that make sense? Or, am I mistaken?
IMHO, making special cases just for certain types of syntax is worse than universal approach. Imagine that \(...\) takes precedence as you say. Then, users may look at it and assume that everything else works the same. And get confused when it does not. Or an opposite - get used to how the rest of markup works just to find out that \(...\) is suddenly different. And that it aside from complicating the parser *a lot*. It is not at all trivial to implement what you want. -- 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>
