Timothy <[email protected]> writes:
> Causes issues. I also note that in the Org-mode buffer the comma seems to
> cause
> issues. I’ve attached a screenshot, in which you can see in the “comma,
> italics”
> situation:
> ⁃ The second line is not italic
> ⁃ The second `/' of the pair is shown (and I have Org’s entity hiding setting
> enabled)
The problem is with org-emph-re.
Our second component of org-emphasis-regexp-components is
> Chars allowed as postmatch. End of line will be allowed too.
"-[:space:].,:!?;'\")}\\["
So, org-element-italic-parser will treat /, sequence as end of the
italic text disregarding that /, is part of the link.
If you try the following text, it will not export correctly as well:
/Beginning is italic 1^{/,} and tail should be italic/
Though fontification somehow works.
Or we can put some other allowed object like inline src block:
/Beginning is italic src_elisp{(message "Foo/,")} and tail should be italic/
This time both export and fontification do not work.
I suspect that we need to upgrade org-element-italic-parser in
non-trivial way to fix this.
Best,
Ihor
