all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Glenn Morris'" <rgm@gnu.org>, <emacs-devel@gnu.org>
Subject: RE: C-h C-b to view "Reporting Bugs" section of the manual
Date: Mon, 21 May 2012 13:53:09 -0700	[thread overview]
Message-ID: <3C645B82A25242F7AF3BE16B9CB9BCAA@us.oracle.com> (raw)
In-Reply-To: <41txz9pboj.fsf@fencepost.gnu.org>

> 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'?

A priori, I would prefer to keep most `C-h' keys for commands that describe
things.  Sooner or later we will have a "b" or "C-b" thingie worth describing
using `C-h C-b'.

Example: In my file `help-fns+.el' I added `C-h M-k' for my `describe-keymap'
command.


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'.

But I've said that before - we should add info links to *Help* output.
There are patches to do that here:
http://lists.gnu.org/archive/html/emacs-devel/2011-06/msg00368.html.




  reply	other threads:[~2012-05-21 20:53 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 [this message]
2012-05-22  0:17   ` Stephen J. Turnbull
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=3C645B82A25242F7AF3BE16B9CB9BCAA@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.