From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: i@introo.me, 22866@debbugs.gnu.org
Subject: bug#22866: 24.5; 'C-h S' leads to inaccurate result
Date: Tue, 01 Mar 2016 18:56:36 +0200 [thread overview]
Message-ID: <83h9gq6ssb.fsf@gnu.org> (raw)
In-Reply-To: <16fa0843-cc8a-4ad4-a627-50ded0d70c3b@default> (message from Drew Adams on Tue, 1 Mar 2016 06:52:53 -0800 (PST))
> Date: Tue, 1 Mar 2016 06:52:53 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
>
> > For the function `delete-char'. 'C-h S' takes me to:
> > (emacs)Top > Killing > Deletion and Killing > Deletion
> > However, it should go to: (elisp)Top > Text > Deletion
>
> Why do you think so? This is a user command, not just an
> Elisp function. An Emacs user looking for information about
> it interactively will expect to go to its description in the
> Emacs manual. If we have to choose one or the other, we
> should, I think, favor user help, especially for a command.
>
> That said... (1) Maybe we could cross-reference the one from
> the other manual? (2) It might be good if `C-h S' popped
> up a buffer of links to references in both manuals. (3) It
> would be good if *Help* output from `C-h f' and `C-h k'
> provided links to the manuals (both).
I think the way to solve this is to have a new Help command that would
specifically look up a function name in the ELisp manual.
next prev parent reply other threads:[~2016-03-01 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 3:23 bug#22866: 24.5; 'C-h S' leads to inaccurate result Shiyao Ma
2016-03-01 14:52 ` Drew Adams
2016-03-01 16:56 ` Eli Zaretskii [this message]
2016-03-01 23:09 ` John Wiegley
2016-03-02 7:44 ` Shiyao Ma
2016-03-02 22:28 ` John Wiegley
2022-01-24 12:00 ` Lars Ingebrigtsen
[not found] <<CAJQX3DxMdTuJeTm2U7s9sAFOFFi5xDsdgOj8UforEnkP9_sUQw@mail.gmail.com>
[not found] ` <<16fa0843-cc8a-4ad4-a627-50ded0d70c3b@default>
[not found] ` <<83h9gq6ssb.fsf@gnu.org>
2016-03-01 17:18 ` 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
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=83h9gq6ssb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22866@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=i@introo.me \
/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).