unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: 9898@debbugs.gnu.org
Subject: bug#9898: 24.0.90; doc of :key-sequence
Date: Fri, 28 Oct 2011 11:48:51 -0700	[thread overview]
Message-ID: <B7475A65554A4B7F8104892076D381EC@us.oracle.com> (raw)

(elisp) Extended Menu Items
 
"`:key-sequence nil'
 This property indicates that there is normally no key binding
 which is equivalent to this menu item.  Using this property saves
 time in preparing the menu for display, because Emacs does not
 need to search the keymaps for a keyboard equivalent for this menu
 item.
 
 However, if the user has rebound this item's definition to a key
 sequence, Emacs ignores the `:keys' property and finds the keyboard
 equivalent anyway."
 
Should that `:keys' be `:key-sequence'?  Since when do we override :keys
with whatever the command is bound to?
 

In GNU Emacs 24.0.90.1 (i386-mingw-nt5.1.2600) of 2011-10-24 on MARVIN
 Windowing system distributor `Microsoft Corp.', version 5.1.2600
 configured using `configure --with-gcc (4.6) --no-opt --cflags
 -I"D:/devel/emacs/libs/libXpm-3.5.8/include"
 -I"D:/devel/emacs/libs/libXpm-3.5.8/src"
 -I"D:/devel/emacs/libs/libpng-dev_1.4.3-1/include"
 -I"D:/devel/emacs/libs/zlib-dev_1.2.5-2/include"
 -I"D:/devel/emacs/libs/giflib-4.1.4-1/include"
 -I"D:/devel/emacs/libs/jpeg-6b-4/include"
 -I"D:/devel/emacs/libs/tiff-3.8.2-1/include"
 -I"D:/devel/emacs/libs/gnutls-2.10.1/include" --ldflags
 -L"D:/devel/emacs/libs/gnutls-2.10.1/lib"'
 






             reply	other threads:[~2011-10-28 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28 18:48 Drew Adams [this message]
2014-02-09  5:58 ` bug#9898: 24.0.90; doc of :key-sequence Lars Ingebrigtsen
2017-03-25  3:22   ` npostavs
2021-07-16 13:52     ` Lars Ingebrigtsen

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=B7475A65554A4B7F8104892076D381EC@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=9898@debbugs.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).