From: Eli Zaretskii <eliz@gnu.org>
To: Kirill Ignatiev <kirill.ignatiev@gmail.com>
Cc: 19266@debbugs.gnu.org
Subject: bug#19266: 24.4; Font-related window redrawing delays on OS X
Date: Thu, 04 Dec 2014 10:03:20 +0200 [thread overview]
Message-ID: <83wq674zav.fsf@gnu.org> (raw)
In-Reply-To: <CACe-pWyVjd3TMe-NL=S-brn7hT3OFE0x7TRrbUMyaUC2aXKkKQ@mail.gmail.com>
> Date: Thu, 4 Dec 2014 02:41:34 -0500
> From: Kirill Ignatiev <kirill.ignatiev@gmail.com>
> Cc: 19266@debbugs.gnu.org
>
> > AFAICT, these delays are due to Emacs searching the system for
> > appropriate fonts needed to display those unusual symbols.
>
> I understand that this needs to happen once.
It can happen once for each portion of a buffer that was not yet
displayed.
> The description of what triggers the delays is unclear because for me
> it's only reproducible incidentally, during normal work. I have
> fold-mode that hides large portions of text, and a number of frames.
> If I hide some previously-displayed text, go work in another frame,
> then come back and unhide the text, then there is the font-searching
> delay. Something similar happens if I switch to a different buffer,
> then some time later switch back.
Emacs releases unused font slots from time to time, which might be the
reason here.
But this is speculation; a reproducible recipe is required to
investigate and come up with specifics. And yes, it could be a bug.
> Is it reasonable to expect to keep all recently used fonts in memory
> and not search for them again?
For some value of "recently", yes. Again, more data is needed to
determine whether this is an Emacs bug or a system configuration
issue.
next prev parent reply other threads:[~2014-12-04 8:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 7:13 bug#19266: 24.4; Font-related window redrawing delays on OS X Kirill Ignatiev
2014-12-04 7:30 ` Eli Zaretskii
2014-12-04 7:41 ` Kirill Ignatiev
2014-12-04 8:03 ` Eli Zaretskii [this message]
2014-12-04 8:20 ` Kirill Ignatiev
2014-12-04 9:55 ` Sebastian Wiesner
2014-12-04 10:17 ` Eli Zaretskii
2014-12-04 10:19 ` Sebastian Wiesner
2014-12-07 5:50 ` Kirill Ignatiev
2014-12-07 16:09 ` Eli Zaretskii
2014-12-10 23:50 ` Kirill Ignatiev
2014-12-11 17:45 ` Eli Zaretskii
2014-12-12 2:10 ` Kirill Ignatiev
2014-12-12 8:06 ` Eli Zaretskii
2014-12-17 1:35 ` Kirill Ignatiev
2014-12-17 2:13 ` Kirill Ignatiev
2014-12-12 8:29 ` Sebastian Wiesner
2014-12-12 9:33 ` Kirill Ignatiev
2014-12-12 10:56 ` Eli Zaretskii
2022-04-30 15:44 ` Lars Ingebrigtsen
2022-05-02 16:22 ` Kirill Ignatiev
2022-05-03 9:05 ` Lars Ingebrigtsen
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=83wq674zav.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19266@debbugs.gnu.org \
--cc=kirill.ignatiev@gmail.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 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).