Re: [BUG] emphasis marker inside macro breaks macro [9.7.16 (release_9.7.16 @ /home/roklein/ot/org-mode/lisp/)]

[Ihor Radchenko <yantar92@posteo.net>]

Robert Klein <roklein@roklein.de> writes:

> When I have an emphasized section with a macro inside and the macro
> contains the emphasis delimiter, macro expansion is broken (i.e. doesn't 
> happen, it is exported verbatim, including the braces and the macro name).
>
> In for / and * the emphasis section ends where the delimiter shows up in the Macro 
> though not for =.
> ...
> - wrong:
>
>   /Open the file {{{Pathname(/ bashrc)}}}/
>
>   /Open the file {{{Pathname(alpha/ bashrc)}}}/
>
>   /Open the file {{{Pathname(~/.bashrc)}}}/
>
>   *bold faced Macro {{{Pathname(*.org)}}}*
>
>   `another {{{Pathname(a = is an equal sign)}}} example'

This is not a bug. You just gave Org ambiguous markup and Org resolved
the ambiguity in a way you did not expect.

    /Open the file {{{Pathname(/ bashrc)}}}/ could be parsed in two ways

   <italics>Open the file <macro>Pathname(/ bashrc)<end macro><end italics> 

or

   <italics>Open the file {{{Pathname(<end italics> bashrc)}}}/

Org happens to use "first matching markup wins" rule, leading to what
you have observed.

You can resolve such ambiguity in two ways:
1. Use zero-width space, as we suggest in https://orgmode.org/manual/Escape-Character.html
2. Use \slash entity to specify slash explicitly where you do not want
   it to be treated as markup delimiter.

Canceled.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
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>