From: Raphael 'kena' Poss <knz@thaumogen.net>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 39390@debbugs.gnu.org
Subject: bug#39390: 28.0.50; prettify-symbols-mode confuses display when start/end faces are different
Date: Mon, 17 Feb 2020 07:35:31 -0500 [thread overview]
Message-ID: <d6f1f393-eaee-5855-31f0-18e11d0c5564@thaumogen.net> (raw)
In-Reply-To: <87ftf931kw.fsf@gnu.org>
Hi Tassilo,
thank you for joining the conversation.
to summarize your standpoint is that:
1) configurations that specify a string are invalid.
2) multi-word matches are "asking for trouble".
Regarding point (1). First of all the function compose-region does
accept a string as per its documentation. Separately if there is
consensus that this type of configuration is invalid, the function
should be programmed to reject it.
Finally, let us not distract ourselves with this detail. The bug is
readily reproducible with a single character:
https://asciinema.org/a/IGDZhOMnmF7sAWJYEjRqPdboA
Regarding point (2). Multiple characters in the output actually works
fine most of the time. Please double check the title of this e-mail
thread and the reason why I reported the issue in the first place:
- replacing either a single character or multiple characters in the
buffer, even separated by blanks, is fine as long as they display with
just 1 face.
- replacing anything with either a single or multiple characters in the
result of the composition is fine as long as the input uses just 1 face.
There is an error in the display code when compose-region composes over
multiple faces, and I'd like us to focus on that. I'm pretty sure that
pretty-symbols-mode is just one of multiple ways one can trigger this bug.
--
Raphael 'kena' Poss
next prev parent reply other threads:[~2020-02-17 12:35 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
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 [this message]
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=d6f1f393-eaee-5855-31f0-18e11d0c5564@thaumogen.net \
--to=knz@thaumogen.net \
--cc=39390@debbugs.gnu.org \
--cc=tsdh@gnu.org \
/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).