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: Sun, 22 Jul 2018 05:45:46 +0000 [thread overview]
Message-ID: <CAAYZpmTCX36Fa2L5qr=aO7t6S=TBpnYM2FHGFkDK-FB=RmTS1A@mail.gmail.com> (raw)
In-Reply-To: <83tvox7vi7.fsf@gnu.org>
On Tue, Jul 17, 2018 at 11:05 PM Eli Zaretskii <eliz@gnu.org> wrote:
> More importantly, if Emacs stops short of finding a font, it will not
> have any useful suggestion for the actual setup of the fontset,
> because it will not know what font to suggest.
Maybe Emacs can prompt the user to find/download the fonts that missing?
> But I think we are getting ahead of ourselves. There could be a place
> for user-level customization commands based on set-fontset-font
> (although I envision non-trivial UI issues, due to the power and
> flexibility of fontsets), but before we discuss that, we should
> establish that customizing fontsets indeed fixes your real-life
> problems. That doing so for some fonts makes HELLO display faster
> doesn't yet mean your real-life use cases are solved by doing the
> same.
>
> So please see if the problems that prompted your bug report are indeed
> solved by customizing your fontset, including determining which
> scripts/ranges of character codepoints needed such customization, and
> let's defer the discussion of more user-friendly facilities to after
> that.
After many failed tries. I finally make Emacs a little faster after
customized the fontset. I have to find the font name and the script
name for each script. It a painful process. Maybe it is not Emacs'
fault, but I hope the customizing process could be automatically done.
The HELLO file opening still slow though.
next prev parent reply other threads:[~2018-07-22 5:45 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
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 [this message]
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
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='CAAYZpmTCX36Fa2L5qr=aO7t6S=TBpnYM2FHGFkDK-FB=RmTS1A@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 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).