Ihor Radchenko writes:
> So, the attached patch is changing the priority of the parsing.
> Maybe Nicolas knows some tricky cases when the patch makes things wrong,
> but those cases are certainly not covered by tests.
No objections.
Applied, onto main, adding ORG-NEWS entry.
https://git.savannah
Ihor Radchenko writes:
> However, thinking about it more, I feel that prioritising underline
> should work better. The underline parser recently got changed into a
> stricter version. Now, only underlines starting after spaces,-,(,',",
> and { are recognised as an underlines.
>
> So, the attached
Juan Manuel Macías writes:
>> The priority appears to be intentional.
>
> I see. But then the compatibility with the rest of the emphasis is
> broken. I mean, the user would expect things like (_underline_) will be
> exported as (\uline{underline}), in the same way that (/emphasis/) is
> exported
Ihor Radchenko writes:
> I am not sure if it is an actual issue.
>
> Note that (_u can be interpreted as a subscript.
> Org prioritises subscript over underline.
>
> Looking at the code:
>
> (?_ (or (and (memq 'subscript restriction)
> (org-element-subscript-parser))
> (and (memq '
Juan Manuel Macías writes:
> I don't know if this is a known issue...
>
> Consider the text:
>
> (_underline_)
I am not sure if it is an actual issue.
Note that (_u can be interpreted as a subscript.
Org prioritises subscript over underline.
Looking at the code:
(?_ (or (and (memq 'subscript
Juan Manuel Macías writes:
> If I do M-! (occur org-match-substring-regexp)
>
> I get:
>
> 10:(_underline_)
> 22:(_underline_ text)
Well, in my case the temporary workaround was to force super/subscripts
with braces:
#+begin_src emacs-lisp
(defun my-org-element-subscript-with-braces-
