unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Run `M-x list-input-methods` and then scroll down the screen in input method panel using the mouse or arrow key will cause Emacs unresponsive for about 1 minite.
Date: Sat, 19 Jun 2021 21:42:09 +0800	[thread overview]
Message-ID: <CAGP6PO+b7-=qayvRfBY_y+9qb2-3Hu_GSYgDSu3xrHi+PXXh+g@mail.gmail.com> (raw)
In-Reply-To: <83r1gyw244.fsf@gnu.org>

On Sat, Jun 19, 2021 at 7:00 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Sat, 19 Jun 2021 13:55:51 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: emacs-devel@gnu.org
> >
> > The fast version is an optimized build, the slow one is unoptimized.
> > That explains at least part of the slowness.  The fast version also
> > doesn't include any text-shaping engine, which might speed up Emacs,
> > but prevents it from correctly displaying complex scripts.
> >
> > What are the Emacs versions of the two builds?
>
> Sorry, I see now that its Emacs 26.3 and 28.
>
> And I guess the Emacs 28 build also used the default optimization
> options, unlike what I said before.

Could you please provide me with the optimization options applicable
to Emacs 28, so that I can give it a try?

>
> So the only difference I see is the text-shaping engine that is
> missing in the "fast" version.  I don't think I understand why that
> should have such a profound effect on the speed of finding fonts,
> sorry.

HY
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
NO. 552 North Gangtie Road, Xingtai, China



  reply	other threads:[~2021-06-19 13:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19  5:05 Run `M-x list-input-methods` and then scroll down the screen in input method panel using the mouse or arrow key will cause Emacs unresponsive for about 1 minite Hongyi Zhao
2021-06-19  6:13 ` Eli Zaretskii
     [not found]   ` <CAGP6PO+5QjiB4jkk1x-VZrhm-gUzEiv7dC_sJH_gi1cRzMGu2Q@mail.gmail.com>
2021-06-19  6:57     ` Eli Zaretskii
2021-06-19  7:16       ` Hongyi Zhao
2021-06-19  9:30         ` Eli Zaretskii
2021-06-19  9:47           ` Hongyi Zhao
2021-06-19 10:03             ` Eli Zaretskii
2021-06-19 10:16               ` Hongyi Zhao
2021-06-19 10:31                 ` Eli Zaretskii
2021-06-19 10:48                   ` Hongyi Zhao
2021-06-19 10:55                     ` Eli Zaretskii
2021-06-19 11:00                       ` Eli Zaretskii
2021-06-19 13:42                         ` Hongyi Zhao [this message]
2021-06-19 13:49                           ` Eli Zaretskii
2021-06-19 14:19                             ` Hongyi Zhao
2021-06-19 14:28                               ` Eli Zaretskii
2021-06-19 15:17                                 ` Hongyi Zhao

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='CAGP6PO+b7-=qayvRfBY_y+9qb2-3Hu_GSYgDSu3xrHi+PXXh+g@mail.gmail.com' \
    --to=hongyi.zhao@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).