From: Eli Zaretskii <eliz@gnu.org>
To: net june <netjune@outlook.com>
Cc: 32159@debbugs.gnu.org
Subject: bug#32159: 26.1; inhibit-compacting-font-caches does not fix all fonts lagging issue
Date: Mon, 16 Jul 2018 17:24:10 +0300 [thread overview]
Message-ID: <831sc39s39.fsf@gnu.org> (raw)
In-Reply-To: <PS1PR04MB28210F5306C09BBD796C5C9FB75D0@PS1PR04MB2821.apcprd04.prod.outlook.com> (message from net june on Mon, 16 Jul 2018 03:43:10 +0000)
> From: net june <netjune@outlook.com>
> Date: Mon, 16 Jul 2018 03:43:10 +0000
>
> Is it possible to save the font search result to file (custom file) for
> next use? Then we just need to open the HELLO file once to cache the result.
I tried to explain in my other mail the downsides of caching font
information. If you use Emacs as intended, i.e. by having a single
session running at all times, the cache is inside Emacs anyway.
next prev parent reply other threads:[~2018-07-16 14:24 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 [this message]
[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
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=831sc39s39.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32159@debbugs.gnu.org \
--cc=netjune@outlook.com \
/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.