From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 55068@debbugs.gnu.org, telegraph@gmx.net
Subject: bug#55068: 29.0.50; crashes when trying to set default font
Date: Mon, 23 May 2022 20:40:02 +0800 [thread overview]
Message-ID: <87ee0kmnh9.fsf@yahoo.com> (raw)
In-Reply-To: <87r14kl934.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 23 May 2022 14:36:15 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Nope; no crashes with that patch, thanks.
>
> (Side note: It is pretty slow, though -- popping up and closing the menu
> both takes about five seconds on this laptop, so perhaps it should limit
> the number of entries in one way or another. And... the family names
> aren't sorted alphabetically? And it looks like I'm getting several
> instances of each family -- it's so slow that it's a bit painful to
> scroll through, but I'm getting several instances of "Lato", for
> instance, at arbitrary places in the list.)
Yes, I agree completely. Allocating 20 MB to generate a popup menu also
seems excessive, but we don't have a way of "lazy-loading" menus at
present.
But for now let's just avoid the crash. I will try to think up
something later that doesn't involve selecting through many different
layers of menus.
Thanks for testing.
next prev parent reply other threads:[~2022-05-23 12:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 18:38 bug#55068: 29.0.50; crashes when trying to set default font Gregor Zattler
2022-04-23 10:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-24 10:34 ` Gregor Zattler
2022-04-24 10:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-24 21:34 ` Gregor Zattler
2022-04-25 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-25 2:29 ` Eli Zaretskii
2022-04-25 3:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 8:01 ` Lars Ingebrigtsen
2022-05-23 9:40 ` Gregor Zattler
2022-05-23 10:27 ` Lars Ingebrigtsen
2022-05-23 11:26 ` Eli Zaretskii
2022-05-23 11:58 ` Lars Ingebrigtsen
2022-05-23 12:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 12:19 ` Lars Ingebrigtsen
2022-05-23 12:24 ` Lars Ingebrigtsen
2022-05-23 12:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 12:36 ` Lars Ingebrigtsen
2022-05-23 12:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-05-23 13:59 ` Eli Zaretskii
2022-05-24 0:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87ee0kmnh9.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=55068@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=telegraph@gmx.net \
/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).