unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 426@emacsbugs.donarmstrong.com
Subject: bug#426: 23.0.60; C-h k <down-mouse-2> in *Calendar* does not work
Date: Mon, 16 Jun 2008 20:50:20 -0400	[thread overview]
Message-ID: <jwvfxrcubtq.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <58F6EFA0-4818-4A9F-9D06-A4BA9EC5BE88@Freenet.DE> (Peter Dyballa's message of "Mon, 16 Jun 2008 23:38:46 +0200")

> There must be more changed. In GNU Emacs 22.2 I can 'C-h
> k <down-mouse-2>' and a *Help* buffer opens telling me (excerpt,
> <mouse-2> left out):

> 	<down-mouse-2> at that spot runs the command calendar-mouse-2-date-menu
> 	  which is an interactive Lisp function in `cal-menu.el'.
> 	It is bound to <down-mouse-2>.
> 	(calendar-mouse-2-date-menu EVENT)

> 'C-h k <down-mouse-3>' in GNU Emacs 23.0.60 does not produce the same
> (telling cal-menu-context-mouse-menu's name). This is consistent with

That's a deliberate change.  Emacs-22 allowed you to figure out which
command brings up a menu whereas Emacs-23 allows you to figure out which
command is triggered by any particular menu entry.

Sadly, you can't easily have both.  But in case you want to know: there
is now *no* command that brings up the menu.  Instead mouse-3 is
directly bound to the menu, without any intervening command.


        Stefan






  reply	other threads:[~2008-06-17  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ts63s8sise.fsf@fencepost.gnu.org>
2008-06-16  9:12 ` bug#426: 23.0.60; C-h k <down-mouse-2> in *Calendar* does not work Peter Dyballa
2008-06-16 18:24   ` Glenn Morris
2008-06-16 20:22     ` Stefan Monnier
2008-06-16 21:38     ` Peter Dyballa
2008-06-17  0:50       ` Stefan Monnier [this message]
2008-06-17  6:10   ` bug#426: marked as done (23.0.60; C-h k <down-mouse-2> in *Calendar* does not work) Emacs bug Tracking System

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=jwvfxrcubtq.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=426@emacsbugs.donarmstrong.com \
    --cc=Peter_Dyballa@Freenet.DE \
    /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).