all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <2873@emacsbugs.donarmstrong.com>,
	"'Stefan Monnier'" <monnier@IRO.UMontreal.CA>
Cc: bug-gnu-emacs@gnu.org, 'Nikolaj Schumacher' <me@nschum.de>
Subject: bug#2873: Keybinding info for remapped commands could be more useful
Date: Fri, 24 Apr 2009 10:04:28 -0700	[thread overview]
Message-ID: <003901c9c4fe$bbd1b5b0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <004301c9b4a7$42e8f030$0200a8c0@us.oracle.com>

> > >> When using a command, Emacs conveniently flashes the keybinding.
> > >> For remapped commands, the message is not as useful:
> > >> You can run the command `command' with <remap> <original-command>
> > >> 
> > >> It would probably be better to offer the binding of 
> > >> original-command instead.
> > 
> > > Sounds related to bug #788, which mentioned the same 
> > > problem for key mentions in menu items.
> > 
> > Indeed.  Back then I suggested to move the fix into 
> > where-is-internal and this bug report seems to show that
> > it would indeed be a good idea.
> 
> Yidong recently made a temporary fix of #788: removing the 
> key mention from such menu items. If and when the bug gets
> fixed properly, we need to remember to revert that temporary
> fix, so such keys will appear again (but properly) in menu
> items. 

BTW, somehow we already DTRT for `C-h f bar', for a command `bar' that is
remapped from command `foo'. The key bindings mentioned for `bar' are correct -
it doesn't just say that `bar' is remapped from `foo'.








  reply	other threads:[~2009-04-24 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03  8:11 bug#2873: Keybinding info for remapped commands could be more useful Nikolaj Schumacher
2009-04-03 14:12 ` Drew Adams
2009-04-03 21:31   ` Stefan Monnier
2009-04-03 21:58     ` Drew Adams
2009-04-24 17:04       ` Drew Adams [this message]
2011-10-05  6:38     ` Glenn Morris

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003901c9c4fe$bbd1b5b0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=2873@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=me@nschum.de \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.