From: Eli Zaretskii <eliz@gnu.org>
To: Will Bush <will.g.bush@gmail.com>
Cc: contovob@tcd.ie, rpluim@gmail.com, 40733@debbugs.gnu.org
Subject: bug#40733: 28.0.50; Emacs locks up on paste (yank) of unicode characters
Date: Tue, 21 Apr 2020 17:29:14 +0300 [thread overview]
Message-ID: <83h7xcgbet.fsf@gnu.org> (raw)
In-Reply-To: <CA+aYz4TicXRvtBchSaNoppPofChEcsBn58m-jEWZwJ1B3uojGg@mail.gmail.com> (message from Will Bush on Tue, 21 Apr 2020 07:19:56 -0500)
> From: Will Bush <will.g.bush@gmail.com>
> Date: Tue, 21 Apr 2020 07:19:56 -0500
> Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 40733@debbugs.gnu.org
>
> I tried Emacs 26.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.17) (A
> version that just happens to be in nixpkgs) again to see what it would do when
> yanking that character with and without google-fonts installed.
>
> With google-fonts installed it doesn't have latency issues, but it inserts an
> empty whitespace looking character (wider than a normal space). Without
> google-fonts installed, it renders the character fine with no latency.
>
> So I suspect even if there is an issue with google-fonts, there's still a
> regression in Emacs since 26.3.
I'm not sure I understand: you are saying that slow, but correct
display is _worse_ than displaying a white space instead of the
correct glyph, i.e. producing incorrect display? To me, it sounds
like Emacs 27+ actually _improves_ things in this case.
prev parent reply other threads:[~2020-04-21 14:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:05 bug#40733: 28.0.50; Emacs locks up on paste (yank) of unicode characters Will Bush
2020-04-20 15:52 ` Robert Pluim
2020-04-20 16:13 ` Eli Zaretskii
2020-04-20 21:27 ` Will Bush
2020-04-20 20:20 ` Alan Third
2020-04-20 22:48 ` Basil L. Contovounesios
2020-04-21 10:01 ` Robert Pluim
2020-04-21 12:19 ` Will Bush
2020-04-21 13:19 ` Robert Pluim
2020-04-21 19:35 ` James Cloos
2020-04-22 7:35 ` Robert Pluim
2020-04-25 10:34 ` Will Bush
[not found] ` <CA+aYz4RNB1-g5uUz-M-XuJEhZPGpA4X6n8NSiTCUdOMkpReFng@mail.gmail.com>
2020-04-25 13:34 ` bug#40733: Fwd: " Will Bush
2020-04-25 13:50 ` Eli Zaretskii
2020-04-29 11:59 ` Will Bush
2020-04-29 12:16 ` Eli Zaretskii
2020-04-29 12:42 ` Will Bush
2020-04-29 12:50 ` Robert Pluim
2020-04-29 14:30 ` Eli Zaretskii
2020-06-01 11:19 ` Will Bush
2020-06-01 11:44 ` Pip Cet
2020-06-01 15:15 ` Eli Zaretskii
2020-06-01 15:50 ` Pip Cet
2022-04-24 14:20 ` Lars Ingebrigtsen
2022-05-18 3:39 ` Will Bush
2022-05-18 11:18 ` Eli Zaretskii
2022-06-15 12:40 ` Lars Ingebrigtsen
2022-06-19 21:05 ` Will Bush
2022-06-19 22:25 ` Lars Ingebrigtsen
2020-04-21 14:29 ` Eli Zaretskii [this message]
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=83h7xcgbet.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40733@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=rpluim@gmail.com \
--cc=will.g.bush@gmail.com \
/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).