From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27350@debbugs.gnu.org
Subject: bug#27350: 25.2; Make `inhibit-compacting-font-caches' customizable
Date: Tue, 13 Jun 2017 10:02:17 -0700 (PDT) [thread overview]
Message-ID: <750f3b75-e3b0-4953-aae1-5635721f5d62@default> (raw)
In-Reply-To: <83fuf43p7m.fsf@gnu.org>
> This variable is a "fire escape": it only exists because we were
> unable to fix some of the situations where the slow-down happens (in
> other cases changing the end-user font configuration fixed the
> problem). Ideally, it will some day go away. Making it a defcustom
> and documenting it will make removing it harder.
I see. In that case, agreed. Perhaps NEWS should characterize it
that way, instead of nearly suggesting that it is a user variable:
"Set this variable to a non-nil value to speed up display of
^^^^^^^^^^^^^^^^^
characters using large fonts, at the price of a larger memory
footprint."
> So no, I don't think we should do what you suggest, leaky postings on
> Stackexchange notwithstanding. (And those postings actually harm the
> project, because all such problems should be reported as bugs,
> allowing us to investigate as many of these problems as possible, and
> hopefully helping us eventually find the culprit. "Solving" them on
> Stackexchange avoids bringing more of such problems to our attention.)
I'm glad I brought it to your attention, in that case. ;-)
You know where to find the person with the problem, if you
want more info about that specific case.
And you can also consider addressing the referenced "GitHub
discussion thread" (I haven't looked at it), either to get
further info about specific problems encountered or to let
folks there know that you would prefer that they raise an
Emacs bug.
Both of those references should presumably help you gather
info about "as many of these problems as possible".
next prev parent reply other threads:[~2017-06-13 17:02 UTC|newest]
Thread overview: 17+ 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 [this message]
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
[not found] <<548efd73-7fb5-45ef-979d-59623d31df3b@default>
[not found] ` <<83fuf43p7m.fsf@gnu.org>
[not found] ` <<750f3b75-e3b0-4953-aae1-5635721f5d62@default>
[not found] ` <<834lvj4qva.fsf@gnu.org>
2017-06-13 20:06 ` bug#27350: " Drew Adams
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=750f3b75-e3b0-4953-aae1-5635721f5d62@default \
--to=drew.adams@oracle.com \
--cc=27350@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).