From: Eli Zaretskii <eliz@gnu.org>
To: Petteri Hintsanen <petterih@iki.fi>
Cc: yandros@gmail.com, emacs-devel@gnu.org
Subject: Re: Manual does not mention dictionary.el
Date: Sat, 23 Nov 2024 15:51:03 +0200 [thread overview]
Message-ID: <86jzcukqig.fsf@gnu.org> (raw)
In-Reply-To: <dd778b42-103a-4038-8f30-c3d738015bed@iki.fi> (message from Petteri Hintsanen on Sat, 23 Nov 2024 15:13:43 +0200)
> Date: Sat, 23 Nov 2024 15:13:43 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> From: Petteri Hintsanen <petterih@iki.fi>
>
> C-h P is news for me, thanks.
>
> > but discovery is a non-trivial problem for roughly everyone
>
> It is, like data management in general.
>
> For me, manuals (texinfo, man pages) are "the" definitive source for
> information about the installed features. Occasionally I use C-h a too,
> as it often catches things that are not mentioned in manuals.
This is not the best practice for Emacs. The Emacs manuals don't
mention all the features, simply because there are too many of them,
and mentioning them all will make the manuals impractically large.
By contrast, the built-in Help commands will return information about
all the features that are either already loaded or auto-loaded.
prev parent reply other threads:[~2024-11-23 13:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 20:13 Manual does not mention dictionary.el Petteri Hintsanen
2024-10-11 21:35 ` Divya
2024-10-11 22:39 ` Juergen Fenn
2024-10-12 7:21 ` Eli Zaretskii
2024-10-12 9:39 ` Petteri Hintsanen
2024-10-12 18:23 ` chad
2024-10-12 18:32 ` Eli Zaretskii
2024-10-12 21:59 ` Joost Kremers
2024-10-13 5:12 ` Eli Zaretskii
2024-10-14 1:39 ` chad
2024-10-14 7:11 ` Joost Kremers
2024-10-14 14:07 ` Eli Zaretskii
2024-10-14 13:50 ` Eli Zaretskii
2024-10-14 18:23 ` chad
2024-10-15 0:46 ` Michael Heerdegen via Emacs development discussions.
2024-10-15 5:30 ` chad
2024-10-15 12:20 ` Eli Zaretskii
2024-10-15 13:14 ` Eli Zaretskii
2024-11-23 13:13 ` Petteri Hintsanen
2024-11-23 13:51 ` Eli Zaretskii [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
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=86jzcukqig.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=petterih@iki.fi \
--cc=yandros@gmail.com \
/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).