From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>,
"'Andreas Schwab'" <schwab@linux-m68k.org>
Cc: 8904@debbugs.gnu.org
Subject: bug#8904: 24.0.50; describe `describe-prefix-bindings' in Emacs manual
Date: Fri, 15 Jul 2011 08:40:32 -0700 [thread overview]
Message-ID: <BBDD061B009D486EB7C7BF6C289A1B39@us.oracle.com> (raw)
In-Reply-To: <m3livz36qe.fsf@quimbies.gnus.org>
> I was not enlightened.
Lars, you need better doc for this command. ;-) Seriously.
To enlighten yourself and thus help in coming up with that doc:
1. See what the Elisp manual says, as the bug report indicated.
2. Consult the code, in help.el.
In #2 you will see this:
;; Make C-h after a prefix, when not specifically bound,
;; run describe-prefix-bindings.
(setq prefix-help-command 'describe-prefix-bindings)
Maybe this will help you see why code comments are not substitutes for doc
strings. Had appropriate info been available to you interactively via `C-h f
describe-prefix-bindings' you would not have needed to ask others or consult the
code.
Now try it:
C-x C-h
C-x RET C-h
M-s C-h
...
Another lesson learned: Not every command is designed to work best with `M-x'.
next prev parent reply other threads:[~2011-07-15 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 17:08 bug#8904: 24.0.50; describe `describe-prefix-bindings' in Emacs manual Drew Adams
2011-07-15 14:21 ` Lars Magne Ingebrigtsen
2011-07-15 15:20 ` Andreas Schwab
2011-07-15 15:26 ` Lars Magne Ingebrigtsen
2011-07-15 15:40 ` Drew Adams [this message]
2011-07-15 15:48 ` Lars Magne Ingebrigtsen
2011-07-15 16:05 ` Drew Adams
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=BBDD061B009D486EB7C7BF6C289A1B39@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8904@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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 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.