unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Stephen Berman <stephen.berman@gmx.net>, 53916@debbugs.gnu.org
Subject: bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu
Date: Thu, 10 Feb 2022 21:03:59 +0800	[thread overview]
Message-ID: <8735kqyitc.fsf@yahoo.com> (raw)
In-Reply-To: <87ee4a7ujw.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 10 Feb 2022 13:52:35 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" <bug-gnu-emacs@gnu.org> writes:
>
>> That warning is harmless, though we could make it go away by installing
>> a log handler.  Someone else should chime in at this point to decide
>> whether or not that's worth it, since such a filter might end up
>> obscuring legitimate problems in the future.
>
> My impression is that most of these warnings from GTK are harmless, so
> perhaps having a log handler (and defaulting it to "off") would be good.
> (But there should be a user option to switch them on.)

I'm okay with doing that for this particular warning, and the
appropriate option already exists (the G_DEBUG environment variable can
be set to `fatal-warnings', which will cause GLib to abort upon
encoutering such a warning, even if we filter it out.)

But I don't know whether or not it's okay to treat all warnings that
way.  For example, bug#53900 is a serious bug that got caught by someone
noticing a warning emitted by GTK, and presumably wouldn't have been
reported if the warning had been filtered out.

Thanks.





  reply	other threads:[~2022-02-10 13:03 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 [this message]
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
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=8735kqyitc.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53916@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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).