From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 27350@debbugs.gnu.org, felix.klee@inka.de
Subject: bug#27350: #27350 25.2; Make `inhibit-compacting-font-caches' customizable
Date: Fri, 13 Sep 2019 16:47:24 +0300 [thread overview]
Message-ID: <83tv9gz4sz.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmn0G6YOTeoRkJXZ60JvQZ+T8+mqUdh=v3nLuFThZU3KpA@mail.gmail.com> (message from Stefan Kangas on Fri, 13 Sep 2019 14:45:33 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 13 Sep 2019 14:45:33 +0200
> Cc: "Felix E. Klee" <felix.klee@inka.de>, 27350-done@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Anyway, if that variable does the trick for you, and you are happy
> > with it, by all means keep using it. That's why I added it. I just
> > hoped we will be able to find a better solution, but I guess not yet.
>
> inhibit-compacting-font-caches is now t by default on Windows. Can we
> therefore close this bug report?
It's fine with me to close it, but the fact that the variable is now
non-nil by default on MS-Windows has nothing to do with the decision
whether to close it. I expressed my opinion about this long ago by
tagging it as wontfix.
Thanks.
prev parent reply other threads:[~2019-09-13 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 14:33 bug#27350: 25.2; Make `inhibit-compacting-font-caches' customizable Drew Adams
2017-06-13 15:02 ` Eli Zaretskii
2017-06-13 17:02 ` Drew Adams
2017-06-13 19:41 ` Eli Zaretskii
2017-06-15 11:53 ` bug#27350: #27350 " Felix E. Klee
2017-06-15 14:38 ` Eli Zaretskii
2017-06-15 15:46 ` Felix E. Klee
2017-06-15 16:01 ` Eli Zaretskii
2017-06-15 16:23 ` Felix E. Klee
2017-06-15 18:23 ` Eli Zaretskii
2017-06-16 10:20 ` Felix E. Klee
2017-06-16 13:00 ` Eli Zaretskii
2017-06-16 13:24 ` Felix E. Klee
2017-06-16 13:47 ` Eli Zaretskii
2019-09-13 12:45 ` Stefan Kangas
2019-09-13 13:47 ` Eli Zaretskii [this message]
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=83tv9gz4sz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27350@debbugs.gnu.org \
--cc=felix.klee@inka.de \
--cc=stefan@marxist.se \
/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).