unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Po Lu <luangruo@yahoo.com>, 53916@debbugs.gnu.org
Subject: bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu
Date: Thu, 10 Feb 2022 14:30:27 +0100	[thread overview]
Message-ID: <87czju3l3g.fsf@gmail.com> (raw)
In-Reply-To: <87iltmyl6d.fsf@yahoo.com> (Po Lu via's message of "Thu, 10 Feb 2022 20:12:58 +0800")

>>>>> On Thu, 10 Feb 2022 20:12:58 +0800, Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> said:

    Po> Stephen Berman <stephen.berman@gmx.net> writes:
    >> 0. emacs -Q
    >> 1. Disable with menu bar with `M-x menu-bar-mode'
    >> 2. Press the F10 key to invoke `menu-bar-open'
    >> => In the shell the following warning is emitted:
    >> 
    >> (emacs-pgtk:6569): Gtk-WARNING **: 11:39:05.713: no trigger event for menu popup

    Po> That warning is harmless, though we could make it go away by installing
    Po> a log handler.  Someone else should chime in at this point to decide
    Po> whether or not that's worth it, since such a filter might end up
    Po> obscuring legitimate problems in the future.

Can such a log handler put those warnings in *Messages*?

Robert
-- 





  parent reply	other threads:[~2022-02-10 13:30 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 [this message]
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=87czju3l3g.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=53916@debbugs.gnu.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).