From: Lars Ingebrigtsen <larsi@gnus.org>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 6436@debbugs.gnu.org
Subject: bug#6436: 23.2; C-h C-h incomprehensible to new users
Date: Wed, 21 Aug 2019 16:41:22 -0700 [thread overview]
Message-ID: <87d0gyulwd.fsf@mouse.gnus.org> (raw)
In-Reply-To: <201006160818.59184.arne_bab@web.de> (Arne Babenhauserheide's message of "Wed, 16 Jun 2010 08:18:51 +0200")
Arne Babenhauserheide <arne_bab@web.de> writes:
> The integrated help in emacs is a great tool for beginners to learn
> emacs, and C-h d, C-h k, C-h m and C-h t are extremely useful.
>
> Sadly the sheer number of help options made it extremely hard for me
> in the beginning to find out what help I really needed. Most times is
> was simply C-h d or C-h k.
>
> So I’d suggest to seperate the help options into two parts: “needed often by
> most people” and “needed only in very specific situations”.
>
> Then just put the first at the beginning of the help output (common help
> options) and in a next paragraph add the rest (advanced help options).
>
> That should make it far easier for beginners to find the help topic they need
> (and I can safely tell people “if you need help, just type C-h C-h”).
(I'm going through old bug reports that have unfortunately gotten no
attention yet.)
I think the difficult thing here would be to figure out what help
commands are needed often and which ones are more obscure. For
instance, I use `C-h f' all the time, and I never use `C-h d', so I
think it just varies.
I don't think there's any really obscure ones until we get to the
`C-h C-' help stuff (like `C-h C-w'), and those are already deempathised
by being last. So I think the current alphabetical organisation makes
the most sense in the long term, and I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-21 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 6:18 bug#6436: 23.2; C-h C-h incomprehensible to new users Arne Babenhauserheide
2019-08-21 23:41 ` Lars Ingebrigtsen [this message]
2019-08-22 4:10 ` Marcin Borkowski
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=87d0gyulwd.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=6436@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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).