From: Ihor Radchenko <firstname.lastname@example.org>
To: Protesilaos Stavrou <email@example.com>
Subject: Re: Possible bug? Combine emphasis marker faces?
Date: Sun, 03 Oct 2021 16:43:27 +0800 [thread overview]
Message-ID: <87zgrq5wi8.fsf@localhost> (raw)
Protesilaos Stavrou <firstname.lastname@example.org> writes:
> Hello everyone,
> I have noticed that it is not possible to combine org-emphasis-alist
> characters. When applying multiple types of emphasis, the face
> corresponding to the outermost pair overrides its innermost counterparts.
> For example, */emphasise/* will render with the 'bold' face, while
> /*emphasise*/ will use the 'italic' face.
> Looking at the code, this seems to be intentional or unavoidable, while
> I do not know of a way to blend faces dynamically.
> Is there a way to get composite styles? Such as bold and italic or
> verbatim and underline, etc.?
org-element-context does return nested emphasis, so it is certainly
possible to combine composite styles (at least, during export).
Fontification code does not work with elements though and I do not see
an easy way to change it.
Rewriting fontification using org-element API would eliminate this type
of issues. However, I am not sure about performance (maybe with
prev parent reply other threads:[~2021-10-03 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 15:14 Possible bug? Combine emphasis marker faces? Protesilaos Stavrou
2021-09-28 16:54 ` Juan Manuel Macías
2021-10-03 8:43 ` Ihor Radchenko [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).