From: Eli Zaretskii <eliz@gnu.org>
To: Raphael 'kena' Poss <knz@thaumogen.net>
Cc: 39390@debbugs.gnu.org
Subject: bug#39390: 28.0.50; prettify-symbols-mode confuses display when start/end faces are different
Date: Sun, 02 Feb 2020 21:20:41 +0200 [thread overview]
Message-ID: <837e14iynq.fsf@gnu.org> (raw)
In-Reply-To: <34ca60a0-3658-0e64-b16f-829d914d4b81@thaumogen.net> (message from Raphael 'kena' Poss on Sun, 2 Feb 2020 19:28:24 +0100)
> Cc: 39390@debbugs.gnu.org
> From: Raphael 'kena' Poss <knz@thaumogen.net>
> Date: Sun, 2 Feb 2020 19:28:24 +0100
>
> Is there a way to tweak either the configuration
> (prettify-symbols-alist) or prog-mode.el to trick it into emitting the
> same face for the substitution?
It sounds like there's a misunderstanding. prettify-symbols-mode
doesn't emit any faces, it "composes" several characters into one or
more symbols. The composition process needs that all of the
characters to be composed have the same face. That face is put on the
characters by font-lock mode, not by prettify-symbols-mode. That is
why I suggested to amend the font-lock definitions for the major
mode(s) you are using. Without all the characters to be replaced
having the same font-lock face, you will not be able to "convince"
prettify-symbols-mode to replace them, because the underlying
mechanism that examines the characters to be composed stops when the
face property changes.
> (My opinion is that this bug exists in prog-mode.el and thus a
> workaround/fix should be provided at that level, not in a per-mode or
> per-user customization.)
It isn't a bug, it is a fundamental limitation of the method used by
prettify-symbols-mode to replace text with symbols.
next prev parent reply other threads:[~2020-02-02 19:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 14:45 bug#39390: 28.0.50; prettify-symbols-mode confuses display when start/end faces are different Raphael 'kena' Poss
2020-02-02 17:18 ` Eli Zaretskii
2020-02-02 17:56 ` Raphael 'kena' Poss
2020-02-02 18:03 ` Eli Zaretskii
2020-02-02 18:28 ` Raphael 'kena' Poss
2020-02-02 19:20 ` Eli Zaretskii [this message]
2020-02-02 20:00 ` Raphael 'kena' Poss
2020-02-02 20:09 ` Eli Zaretskii
2020-02-02 20:26 ` Raphael 'kena' Poss
2020-02-03 15:50 ` Eli Zaretskii
2020-02-04 22:07 ` Raphael 'kena' Poss
2020-02-16 17:46 ` Eli Zaretskii
2020-02-16 18:37 ` Raphael 'kena' Poss
2020-02-16 19:29 ` Eli Zaretskii
2020-02-16 19:34 ` Eli Zaretskii
2020-02-16 19:40 ` Raphael 'kena' Poss
2020-02-16 20:23 ` Eli Zaretskii
2020-02-17 2:47 ` Raphael 'kena' Poss
2020-02-17 11:17 ` Tassilo Horn
2020-02-17 12:35 ` Raphael 'kena' Poss
2020-02-17 15:59 ` Tassilo Horn
2020-02-17 16:06 ` Raphael 'kena' Poss
2020-02-17 17:30 ` Eli Zaretskii
2020-02-17 18:37 ` Raphael 'kena' Poss
2020-02-17 19:24 ` Eli Zaretskii
2020-02-17 19:28 ` Raphael 'kena' Poss
2020-02-17 20:14 ` Eli Zaretskii
2020-02-17 17:11 ` Eli Zaretskii
2020-02-17 17:13 ` Eli Zaretskii
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837e14iynq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39390@debbugs.gnu.org \
--cc=knz@thaumogen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs.git
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).