From: Eli Zaretskii <eliz@gnu.org>
To: Raphael 'kena' Poss <knz@thaumogen.net>
Cc: tsdh@gnu.org, 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 21:24:03 +0200 [thread overview]
Message-ID: <834kvpm2zw.fsf@gnu.org> (raw)
In-Reply-To: <d107d0cf-8570-e411-9b41-9f3eeedb195a@thaumogen.net> (message from Raphael 'kena' Poss on Mon, 17 Feb 2020 13:37:07 -0500)
> Cc: 39390@debbugs.gnu.org
> From: Raphael 'kena' Poss <knz@thaumogen.net>
> Date: Mon, 17 Feb 2020 13:37:07 -0500
>
> On 17-02-2020 12:30, Eli Zaretskii wrote:
> > So this limitation is not
> > really arbitrary, and can only be lifted by a thorough redesign of how
> > the display engine traverses the text it is about to display, and what
> > it does when it meets a composition that crosses face boundaries.
>
> My humble opinion on this is that either the compose function should
> report an exception / error, or pick some arbitrary behavior (e.g. just
> use the 1st face for the entire substitution) and use that.
We cannot raise an exception inside redisplay, because that would
produce an infinite sequence of error messages (each error message
requires a redisplay cycle -- to display the message -- which then
again raises the same exception).
> It seems strange to me to accept the current non-deterministic,
> display-corrupting behavior as a reasonable alternative.
We are talking about 2 different things. I was talking about
composing characters across face changes, whereas you were talking
about handling invalid composition rules, such as the one you tried to
use.
next prev parent reply other threads:[~2020-02-17 19:24 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
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 [this message]
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=834kvpm2zw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39390@debbugs.gnu.org \
--cc=knz@thaumogen.net \
--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).