all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Moses <moses.mason@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32159@debbugs.gnu.org
Subject: bug#32159: 26.1; inhibit-compacting-font-caches does not fix all fonts lagging issue
Date: Tue, 17 Jul 2018 12:22:27 +0800	[thread overview]
Message-ID: <CAAYZpmS2AiMGR56ZTMQjTa3dodtMEvG7Gkw3xXphDFQHO5Gr+A@mail.gmail.com> (raw)
In-Reply-To: <83y3ea7ff4.fsf@gnu.org>

On Tue, Jul 17, 2018 at 10:40 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > How to get the correct second argument (script name?)
> It is shown by "C-u C-x =".

OK. I see it now. The info is somewhat not obvious to me.

> > and also the "iso10646-1" (encoding name?)?
> Always use iso10646-1, it makes no sense to use anything else with
> these scripts.

How could a user know that? This should at least put into the manual.

> > I do not find it in C-u C-x = and the manual is not very clear about
> > that. Anyway, why Emacs can not generate a "suggestion" of
> > set-fontset-font in the first place and tell user to add it into
> > .emacs?
> It does, in a way: look at the output of "C-u C-x =".  Besides, how is
> Emacs to know that what happens on your system now is a permanent
> setup?

It needn't be a permanent setup. If Emacs loading time becomes longer
(for example, > 5 sec.), it should prompt users to change their
fontset and give suggestion settings again.
BTW, I still confused why Emacs needs to scan fonts to determine which
character belongs to which font. On the other hand, browsers like
Firefox, Chromium could display every script fonts very fast without
issue.





  reply	other threads:[~2018-07-17  4:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15  0:02 bug#32159: 26.1; inhibit-compacting-font-caches does not fix all fonts lagging issue Moses
2018-07-15  2:39 ` Eli Zaretskii
2018-07-15  5:50   ` Moses
2018-07-15 14:41     ` Eli Zaretskii
2018-07-16  2:35       ` Moses
2018-07-16  3:34         ` Eli Zaretskii
2018-07-17  1:38           ` Moses
2018-07-17  2:38             ` Eli Zaretskii
     [not found]     ` <<83in5ga7dc.fsf@gnu.org>
2018-07-15 16:50       ` Drew Adams
2018-07-15 18:53         ` Eli Zaretskii
2018-07-16  3:43           ` net june
2018-07-16 14:24             ` Eli Zaretskii
     [not found]     ` <<<83in5ga7dc.fsf@gnu.org>
     [not found]       ` <<0c4b0a47-267d-4c4d-8d1f-6a562ac7519b@default>
     [not found]         ` <<837elw9vp9.fsf@gnu.org>
2018-07-15 19:43           ` Drew Adams
2018-07-16 14:22             ` Eli Zaretskii
2018-07-17  2:13               ` Moses
2018-07-17  2:40                 ` Eli Zaretskii
2018-07-17  4:22                   ` Moses [this message]
2018-07-17 15:05                     ` Eli Zaretskii
2018-07-19 13:41                       ` Eli Zaretskii
2018-07-19 15:56                         ` Drew Adams
2018-07-22  5:45                       ` Moses
2018-07-22 14:06                         ` Eli Zaretskii
2018-07-22 14:52                           ` Moses
2018-07-22 15:14                             ` Eli Zaretskii
2018-07-22 15:41                               ` Moses
2018-07-22 16:02                                 ` Eli Zaretskii
2018-07-17 10:24 ` Andy Moreton
2018-07-17 15:52   ` 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=CAAYZpmS2AiMGR56ZTMQjTa3dodtMEvG7Gkw3xXphDFQHO5Gr+A@mail.gmail.com \
    --to=moses.mason@gmail.com \
    --cc=32159@debbugs.gnu.org \
    --cc=eliz@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 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.