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: Colin Baxter <m43cap@yandex.com>,
Gregory Heytings <gregory@heytings.org>,
46990@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build
Date: Mon, 20 Jun 2022 18:17:47 +0800 [thread overview]
Message-ID: <87ilovocz8.fsf@yahoo.com> (raw)
In-Reply-To: <871qvj4pgc.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 20 Jun 2022 12:08:35 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I guess that makes sense on some level -- -Q doesn't control what Gtk
> does with the toolbar, for instance. It's still somewhat odd-looking
> for Lucid -- is there any way we can stop it from consulting the X
> resources, or is that completely out of our hands?
It can, but I'd rather not go down the rabbit hole of modifying the
behavior of xrdb.c based on the value of `inhibit-x-resources'.
Different versions of Xlib have different bugs in that area, just look
at this mess in xterm.c:
/* Whether or not XCloseDisplay destroys the associated resource
database depends on the version of libX11. To avoid both
crash and memory leak, we dissociate the database from the
display and then destroy dpyinfo->rdb ourselves.
Unfortunately, the above strategy does not work in some
situations due to a bug in newer versions of libX11: because
XrmSetDatabase doesn't clear the flag XlibDisplayDfltRMDB if
dpy->db is NULL, XCloseDisplay destroys the associated
database whereas it has not been created by XGetDefault
(Bug#21974 in freedesktop.org Bugzilla). As a workaround, we
don't destroy the database here in order to avoid the crash
in the above situations for now, though that may cause memory
leaks in other situations. */
#if false
#ifdef HAVE_XRMSETDATABASE
XrmSetDatabase (dpyinfo->display, NULL);
#else
dpyinfo->display->db = NULL;
#endif
/* We used to call XrmDestroyDatabase from x_delete_display, but
some older versions of libX11 crash if we call it after
closing all the displays. */
XrmDestroyDatabase (dpyinfo->rdb);
#endif
Besides, it would be slightly more annoying to debug the Lucid toolkit
that way.
next prev parent reply other threads:[~2022-06-20 10:17 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 16:57 bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build Colin Baxter
2021-03-08 8:26 ` martin rudalics
2021-03-08 10:05 ` Colin Baxter
2021-03-08 10:56 ` Basil L. Contovounesios
2021-03-08 14:29 ` Colin Baxter
2021-03-08 20:36 ` Glenn Morris
2021-03-10 18:59 ` Colin Baxter
2021-03-10 19:12 ` Eli Zaretskii
2021-03-10 18:41 ` Eli Zaretskii
2021-03-10 19:39 ` Colin Baxter
2021-03-10 20:03 ` Eli Zaretskii
2021-03-10 20:30 ` Colin Baxter
2021-03-10 20:49 ` Eli Zaretskii
2021-03-10 23:34 ` Gregory Heytings
2021-03-11 5:07 ` Eli Zaretskii
2021-03-11 12:56 ` Colin Baxter
2021-03-11 13:23 ` Colin Baxter
2021-03-11 14:02 ` Eli Zaretskii
2021-03-11 14:25 ` Gregory Heytings
2021-03-11 14:50 ` Eli Zaretskii
2022-06-20 8:27 ` Lars Ingebrigtsen
2022-06-20 9:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 9:53 ` Lars Ingebrigtsen
2022-06-20 10:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 10:08 ` Lars Ingebrigtsen
2022-06-20 10:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-20 10:40 ` Lars Ingebrigtsen
2022-06-20 13:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 15:39 ` Lars Ingebrigtsen
2022-06-22 8:29 ` Colin Baxter
2022-06-20 10:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 10:28 ` Lars Ingebrigtsen
2022-06-20 11:02 ` Colin Baxter
2022-06-20 11:07 ` Lars Ingebrigtsen
2022-06-20 12:14 ` Visuwesh
2022-06-20 12:29 ` Colin Baxter
2022-06-20 13:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 13:16 ` Visuwesh
2022-06-20 13:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 13:26 ` Visuwesh
2022-06-20 13:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 15:38 ` Lars Ingebrigtsen
2022-06-20 15:54 ` Eli Zaretskii
2022-06-21 10:16 ` Lars Ingebrigtsen
2022-06-21 12:30 ` Manuel Giraud
2022-06-21 12:36 ` Eli Zaretskii
2022-06-21 13:58 ` Manuel Giraud
2022-06-21 12:36 ` Lars Ingebrigtsen
2022-06-21 1:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 13:01 ` 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=87ilovocz8.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=46990@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=m43cap@yandex.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).