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 12:23:28 +0900 [thread overview]
Message-ID: <87bolgq4pb.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <9404D5B04C754DFAA8733E1027D8BDF5@us.oracle.com>
Drew Adams writes:
> 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).
Well, isn't that basic functionality already available as
`Info-elisp-ref' (aka C-h C-f in my emacs)? Again (in my emacs) when
I use C-h f to get the docstring (which defaults to using the symbol
at point already), point ends up on the name of the function in the
help buffer, so C-h C-f RET takes me to the manual. Links are more
discoverable, I suppose, but they're also annoying because they're
always in your face. They also require moving the mouse, which direct
invocation of Info-elisp-ref won't (because if you invoked
`describe-function' via the mouse, the pointer is most likely on the
function in the source buffer).
It's not clear to me that adding links to the original function's
documentation (as opposed to links to docs for other symbols that are
referenced in the help buffer) is doing anybody any favors.
next prev parent reply other threads:[~2012-05-22 3:23 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
2012-05-22 3:23 ` Stephen J. Turnbull [this message]
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=87bolgq4pb.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.