From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stephen J. Turnbull'" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: RE: C-h C-b to view "Reporting Bugs" section of the manual
Date: Mon, 21 May 2012 18:57:41 -0700 [thread overview]
Message-ID: <9404D5B04C754DFAA8733E1027D8BDF5@us.oracle.com> (raw)
In-Reply-To: <87hav9oyq3.fsf@uwakimon.sk.tsukuba.ac.jp>
> > `C-h M-k' for `describe-keymap'
>
> Speaking of redundant bindings (C-h m ...)
Not at all. Have you tried it? There is nothing similar anywhere, AFAIK. It
is not like `C-x b' (current bindings, all maps) or `C-h m' (mode description -
variable and always incomplete wrt a keymap). Try finding the keys bound in a
minibuffer keymap, in a human-readable form.
The closest thing you have is for a prefix key: `C-x C-h'. The point with `C-h
M-k' is to "see" the bindings for a given keymap variable. (Yes, that's
probably more useful for Emacs programmers than the average Emacs user.)
> > Instead of binding `C-h C-b' to take you to (emacs)
> > `Bugs', I'd sooner see us add a link to (emacs) `Bugs' in
> > the doc string of `report-emacs-bug'.
>
> Why there? That has the same problems as above (except that links
> aren't a scarce resource). The link should be in the blurb that
> appears when you invoke r-e-b, where it is obviously useful and
> usefully obvious.
That could be useful too. It's not either/or.
When you look for the doc about a command (including `r-e-b'), why not have
immediately a set of links to its doc in the manuals (with the manual names and
nodes in the links).
next prev parent reply other threads:[~2012-05-22 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 19:38 C-h C-b to view "Reporting Bugs" section of the manual Glenn Morris
2012-05-21 20:53 ` Drew Adams
2012-05-22 0:17 ` Stephen J. Turnbull
2012-05-22 1:57 ` Drew Adams [this message]
2012-05-22 3:23 ` Stephen J. Turnbull
2012-05-22 5:27 ` Drew Adams
2012-05-23 3:22 ` Stephen J. Turnbull
2012-05-22 4:12 ` Stephen J. Turnbull
2012-05-22 5:28 ` Drew Adams
2012-05-22 6:59 ` 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
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=9404D5B04C754DFAA8733E1027D8BDF5@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).