From: Marcin Borkowski <mbork@mbork.pl>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Arne Babenhauserheide <arne_bab@web.de>, 6436@debbugs.gnu.org
Subject: bug#6436: 23.2; C-h C-h incomprehensible to new users
Date: Thu, 22 Aug 2019 06:10:26 +0200 [thread overview]
Message-ID: <87tva9u9fx.fsf@mbork.pl> (raw)
In-Reply-To: <87d0gyulwd.fsf@mouse.gnus.org>
On 2019-08-22, at 01:41, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> 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.
FWIW, I've been using Emacs for about 20 years, and I just learned (or
maybe relearned) about C-h C-d. OTOH, I've been using C-h k (but also
C-h f, C-h m, C-h w and some others) quite often for many, many years.
Best,
--
Marcin Borkowski
http://mbork.pl
prev parent reply other threads:[~2019-08-22 4:10 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
2019-08-22 4:10 ` Marcin Borkowski [this message]
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=87tva9u9fx.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=6436@debbugs.gnu.org \
--cc=arne_bab@web.de \
--cc=larsi@gnus.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.