Re: [parser] subscripts and underlines interacting badly

[Nicolas Goaziou <n.goaziou@gmail.com>]

Hello,

Aaron Ecay <aaronecay@gmail.com> writes:

> Since the present syntax is inadequate for representating these
> sequences, the new syntax will have to break backwards compatibility
> somehow in order to fix the problem.  So there’s no long-term harm in
> having a short-term kludge that will eventually disappear.

OK. Thanks for the patch.

Though, I think you are patching the wrong location. Modifying
`org-element--get-next-object-candidates' is expensive. It would be
better to patch `org-element-sub/superscript-successor' and make it
ignore underline matches with brackets followed by an underscore
character and resume searching.

> But eventually it will (assuming the cache implementation proves robust
> enough), right?  So, changes in org-element.el will eventually percolate
> to the rest of org, whereas changes elsewhere will wither and dry up.

But it will be a slow process, and, meanwhile both org-element and the
rest of Org must be handled.

> I don’t think escaped characters help with the problem that it is
> presently impossible to represent the following (pseudo)-element
> sequence in org syntax:

[...]

You are right, escaped characters cannot help us here.

> Anyway, what do escaped characters do that entities cannot?  

Not much. But they could be used in verbatim context. Also, they are
somehow inconvenient to use, as you noticed. This can be troublesome in
an environment also meant for note-taking.


Regards,

-- 
Nicolas Goaziou