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, 16 Feb 2020 22:23:17 +0200 [thread overview]
Message-ID: <83k14mmgcq.fsf@gnu.org> (raw)
In-Reply-To: <50e865ca-58f4-7111-65de-15be80741357@thaumogen.net> (message from Raphael 'kena' Poss on Sun, 16 Feb 2020 14:40:04 -0500)
> Cc: 39390@debbugs.gnu.org
> From: Raphael 'kena' Poss <knz@thaumogen.net>
> Date: Sun, 16 Feb 2020 14:40:04 -0500
>
> 1) so you agree there's a discrepancy between the configuration (which
> should generate a _double_ @) and the display (which displays just one
> @). I am expecting the result of the composition to display two @'s. I
> would like to understand where this discrepancy comes from.
Your original report was about display problems with cursor motion, so
I didn't look into the issue of 1 vs 2 @'s, mainly because I wasn't
sure I reproduce the correct situation.
> 2) after we settle on what's the expected _display_ you can still see
> the display bug as per my further instructions. I am still observing
> inconsistent redraws, and I'd like to understand where they come from.
I don't see any display problems.
> 3) My original report was that _regardless of the intended result
> display_ (either one or two chars or more), there is a refresh/redisplay
> bug when the cursor moves across the composition. Instead of focusing on
> the number of characters on the result of composition, I'd like to focus
> on the display bug. If you do not observe the display bug with this
> particular example config
I don't.
> I can produce a dozen alternate configurations that demonstrate the
> bug, with screen recordings of each.
Please do, and thanks.
next prev parent reply other threads:[~2020-02-16 20:23 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k14mmgcq.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.