From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: rpluim@gmail.com, stephen.berman@gmx.net, 53916@debbugs.gnu.org
Subject: bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu
Date: Fri, 11 Feb 2022 10:10:42 +0200 [thread overview]
Message-ID: <83y22hsu0t.fsf@gnu.org> (raw)
In-Reply-To: <87a6exvp8i.fsf@yahoo.com> (message from Po Lu on Fri, 11 Feb 2022 15:25:49 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: rpluim@gmail.com, stephen.berman@gmx.net, 53916@debbugs.gnu.org
> Date: Fri, 11 Feb 2022 15:25:49 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Why confusing? We already have in Emacs 28 and later a buffer named
> > *Async-native-compile-log* that "suddenly appears" as soon as Emacs
> > needs for the first time to natively-compile a Lisp file. How is this
> > case different?
>
> That one is a log of things Emacs is doing, while this one usually
> appears without context, and could contain scary error messages from
> various different libraries.
I don't see the crucial difference.
From my POV, having GTK messages in *Messages* will make debugging
Emacs's own problems harder. Some redisplay problems are only
visible in *Messages* (because we cannot signal an error), and having
the buffer filled up by irrelevant GTK stuff will make reading the
messages harder, and could even make the important messages disappear,
if the GTK stuff overflows message-log-max.
So I really prefer a separate buffer.
next prev parent reply other threads:[~2022-02-11 8:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 10:43 bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu Stephen Berman
2022-02-10 12:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 12:52 ` Lars Ingebrigtsen
2022-02-10 13:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 6:20 ` Lars Ingebrigtsen
2022-02-11 6:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 6:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 7:59 ` Eli Zaretskii
2022-02-11 11:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 13:30 ` Robert Pluim
2022-02-10 13:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 17:40 ` Eli Zaretskii
2022-02-11 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 7:18 ` Eli Zaretskii
2022-02-11 7:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 8:10 ` Eli Zaretskii [this message]
2022-02-11 11:12 ` 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=83y22hsu0t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53916@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=rpluim@gmail.com \
--cc=stephen.berman@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).