From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 3529@emacsbugs.donarmstrong.com
Subject: bug#3529: 23.0.94; C-h k mouse-1 on mode-line fields with menus brings up the menu
Date: Fri, 26 Jun 2009 17:14:18 -0700 [thread overview]
Message-ID: <A1B21F44B0AB4BDEB51BD0E7693E2CD1@us.oracle.com> (raw)
In-Reply-To: <jwv7hyyk0lf.fsf-monnier+emacsbugreports@gnu.org>
> > It should describe mouse-1 at that point. It should not
> > just bring up the menu. IOW, it should act just like
> > C-h k mouse-1 does when you click the buffer name: give
> > you info about what mouse-1 does at that position.
>
> The current behavior was made specifically so that C-h k can
> be used to
> figure out which command is run by a given menu entry. I
> agree that it
> can sometimes be useful to figure what the name of the menu, but
> currently Emacs does provide any way for the user to
> distinguish between
> the two cases, so depending on how you define the menu (either as
> a keymap or as a commmand that pops up a menu), you can
> either find info
> about the bindings in the menu, or info about the menu itself.
>
> I personally need info about the bindings a lot more often than info
> about the menus, which is why we have the current behavior.
>
> It's also in line with the behavior of C-h k for menubar menus.
My bad. I misunderstood. For some reason (duh), I didn't think to choose a menu
item. I thought it was just doing the same thing as clicking mouse-1, instead of
providing help. Dunno why I didn't figure it out. This change was a good one.
prev parent reply other threads:[~2009-06-27 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 21:11 bug#3529: 23.0.94; C-h k mouse-1 on mode-line fields with menus brings up the menu Drew Adams
2009-06-27 0:03 ` Stefan Monnier
2009-06-27 0:14 ` Drew Adams [this message]
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=A1B21F44B0AB4BDEB51BD0E7693E2CD1@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=3529@emacsbugs.donarmstrong.com \
--cc=monnier@iro.umontreal.ca \
/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).