unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16565@debbugs.gnu.org
Subject: bug#16565: 24.3.50; x-popup-menu just returns nil
Date: Tue, 28 Jan 2014 04:11:42 +0100	[thread overview]
Message-ID: <87ppnc7qc1.fsf@web.de> (raw)
In-Reply-To: <874n4ptfhy.fsf@web.de> (Michael Heerdegen's message of "Mon, 27 Jan 2014 20:02:33 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Will try to do that today, thanks.

Ok, I tried to do my best to understand the C code and GUD.

If I understand correctly, this is executed for me:

    selection = xmenu_show (f, xpos, ypos, for_click,
			    keymaps, title, &error_name);

In the good case, SELECTION is bound to different integers, in the bad
case, it is always the same integer, which seems to mean "nil".

But there is a difference in the arguments of the xmenu_show call.  In
the bad case calling with an event:

  (x-popup-menu event (mouse-menu-bar-map))

FOR_CLICK is bound to true.  In the good case with

  (x-popup-menu t (mouse-menu-bar-map))

FOR_CLICK is bound to false.

That made me wonder what happened when I bind `foo' to a mouse-down
event.  Then the bug doesn't happen, `foo' doesn't return nil.


HTH,

Michael.





  reply	other threads:[~2014-01-28  3:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27  2:50 bug#16565: 24.3.50; x-popup-menu just returns nil Michael Heerdegen
2014-01-27  3:05 ` Michael Heerdegen
2014-01-27 16:10 ` Eli Zaretskii
2014-01-27 19:02   ` Michael Heerdegen
2014-01-28  3:11     ` Michael Heerdegen [this message]
2014-01-28  3:47       ` Eli Zaretskii
2014-01-28  5:39         ` Michael Heerdegen
2014-01-28 16:31           ` Eli Zaretskii
2014-01-29  8:27             ` Jan Djärv
2014-01-29 19:26               ` Michael Heerdegen

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=87ppnc7qc1.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=16565@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).