From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: RE: C-h C-b to view "Reporting Bugs" section of the manual
Date: Tue, 22 May 2012 09:17:56 +0900 [thread overview]
Message-ID: <87hav9oyq3.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <3C645B82A25242F7AF3BE16B9CB9BCAA@us.oracle.com>
Drew Adams writes:
> > Any objection to a new C-h C-b binding, to jump to the
> > "Reporting Bugs" section of the manual:
>
> No great objection, but I'd rather not use a help key up for that. Will you
> also want to bind a `C-h' key for (emacs) `Language Help'? And for (emacs)
> `Apropos'? And for (emacs) `Coding Systems'?
Different issue. Binding a key to Reporting Bugs is not for the user
who strokes it, but for the developer who reads the reports.
The problem is that this is not very discoverable; I would guess that
the people who know where to find it don't actually need it.
Furthermore, the need for a quick link will decay rapidly for most
users.
> Example: In my file `help-fns+.el' I added `C-h M-k' for my `describe-keymap'
> command.
Speaking of redundant bindings (C-h m ...)
> 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.
next prev parent reply other threads:[~2012-05-22 0:17 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 [this message]
2012-05-22 1:57 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hav9oyq3.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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 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.