GNU bug report logs - #40733
28.0.50; Emacs locks up on paste (yank) of unicode characters

Previous Next

Package: emacs;

Reported by: Will Bush <will.g.bush <at> gmail.com>

Date: Mon, 20 Apr 2020 14:56:02 UTC

Severity: normal

Tags: moreinfo

Found in version 28.0.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #32 received at 40733 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Will Bush <will.g.bush <at> gmail.com>
Cc: contovob <at> tcd.ie, rpluim <at> gmail.com, 40733 <at> debbugs.gnu.org
Subject: Re: bug#40733: 28.0.50;
 Emacs locks up on paste (yank) of unicode characters
Date: Tue, 21 Apr 2020 17:29:14 +0300
> From: Will Bush <will.g.bush <at> gmail.com>
> Date: Tue, 21 Apr 2020 07:19:56 -0500
> Cc: "Basil L. Contovounesios" <contovob <at> tcd.ie>, 40733 <at> 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.




This bug report was last modified 3 years and 28 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.