From: Werner LEMBERG <wl@gnu.org>
To: rpluim@gmail.com
Cc: schwab@linux-m68k.org, benkasminbullock@gmail.com, 46508@debbugs.gnu.org
Subject: bug#46508: 27.1; Emacs doesn't like ⿰
Date: Tue, 16 Feb 2021 10:28:32 +0100 (CET) [thread overview]
Message-ID: <20210216.102832.1776774814146392935.wl@gnu.org> (raw)
In-Reply-To: <87mtw4v1sb.fsf@gmail.com>
> Ben> This caused the problem to occur again and emacs -Q stalled
> Ben> completely. I then restarted emacs with emacs -Q without
> Ben> opening the problem file (which contains a single ⿰). In the
> Ben> new Emacs window I copy-pasted the above code and ran
> Ben> 'eval-buffer' then I used C-x C-f to load the file containing
> Ben> the ⿰ single character. I then started typing this email, and
> Ben> it is still unable to load the file containing the ⿰ even as I
> Ben> am typing now. It finally loaded after several minutes, but the
> Ben> ⿰ character is not displayed, instead there is a box with 2FF0
> Ben> in it.
>
> I have no problems displaying that codepoint, because I have a
> scalable font installed that can display the character, [...]
Exactly. However, this is not always the case, and the freeze of
Emacs is very, very annoying. Other applications like my KDE terminal
is stalled only for approx. a second in similar situations.
Is there something that could be done on the Emacs side to improve its
behaviour? For example, putting the font retrieving process into a
separate thread, providing a dummy glyph until the real one is
available? Or maybe something else? What does the terminal do to be
so much faster?
Werner
next prev parent reply other threads:[~2021-02-16 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 3:32 bug#46508: 27.1; Emacs doesn't like ⿰ Ben Bullock
2021-02-14 11:55 ` Andreas Schwab
2021-02-14 20:50 ` Ben Bullock
2021-02-15 8:23 ` Andreas Schwab
2021-02-16 7:14 ` Ben Bullock
2021-02-16 8:45 ` Robert Pluim
2021-02-16 9:28 ` Werner LEMBERG [this message]
2021-02-16 15:28 ` 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=20210216.102832.1776774814146392935.wl@gnu.org \
--to=wl@gnu.org \
--cc=46508@debbugs.gnu.org \
--cc=benkasminbullock@gmail.com \
--cc=rpluim@gmail.com \
--cc=schwab@linux-m68k.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 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.