unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 50936@debbugs.gnu.org
Subject: bug#50936: "(emacs) Help" does say how to find external packages
Date: Fri, 01 Oct 2021 15:31:20 +0300	[thread overview]
Message-ID: <83mtntdizr.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=qBzYD89ZcK62JVOwXhQrzfiBW+3txRVf83BO23ZUsGw@mail.gmail.com> (message from Stefan Kangas on Fri, 1 Oct 2021 13:48:57 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 1 Oct 2021 13:48:57 +0200
> 
> In (info "(emacs) Help"), I read:
> 
>      If you are looking for a certain feature, but don’t know what it is
>   called or where to look, we recommend three methods.  First, try an
>   apropos command, then try searching the manual index, then look in the
>   FAQ and the package keywords.
>   [...]
>   ‘C-h p’
>        This displays the available Emacs packages based on keywords.
>        *Note Package Keywords::.
> 
> The problem with this is that packages from GNU ELPA and NonGNU ELPA
> aren't listed here, so the better place to look should actually be
> 'M-x list-packages'.  Because that's where you'll find important modes
> for programming languages, etc.

"Modes" and "features" are not the same.  The latter refers to
features built into Emacs, i.e. to bundled packages.  If that isn't
clear from the text, we could clarify that, although it should be
quite obvious that an Emacs manual talks about bundled features.

> I'm not sure if the recommendation should be changed, or simply
> amended to also mention M-x list-packages.

It's okay to also mention list-packages, but if so, the text should
explicitly say that it's for features and packages not included in
the core distribution.

More importantly, I think we should seriously consider whether such
text has its place in that section.  That section is supposed to be a
cookbook for quickly and efficiently find Emacs features, so it should
be limited to methods and commands that accurate, in the sense that
they don't present the user with long lists of potential hits.  By
contrast, list-packages shows a very long list of packages (more than
400 as of this writing), which can easily overwhelm the user.  Even
"C-h p" doesn't show such long lists (the longest has 50 items), and
it is already too long, which is why it's the last in the list of
recommended methods.

> Or perhaps finder should list packages that are not installed?

Wouldn't that make "C-h p" less efficient, for the reason pointed out
above?





  reply	other threads:[~2021-10-01 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 11:48 bug#50936: "(emacs) Help" does say how to find external packages Stefan Kangas
2021-10-01 12:31 ` Eli Zaretskii [this message]
2021-10-01 13:15   ` Stefan Kangas
2021-10-01 13:28     ` Eli Zaretskii
2021-10-01 14:42       ` Stefan Kangas
2021-10-01 15:46         ` Eli Zaretskii
2021-10-01 17:28           ` Stefan Kangas
2021-10-01 17:54             ` Eli Zaretskii
2022-09-03 12:46   ` Lars Ingebrigtsen

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=83mtntdizr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50936@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).