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 16:28:49 +0300 [thread overview]
Message-ID: <83ee94euwe.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnVCSDMQNyjiTB52i0yaFA_Y7Y+WoEOEaCNCK7VtRmx9Q@mail.gmail.com> (message from Stefan Kangas on Fri, 1 Oct 2021 15:15:26 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 1 Oct 2021 15:15:26 +0200
> Cc: 50936@debbugs.gnu.org
>
> > 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.
>
> That's a problem, but there is IMO no way around that as long as Emacs
> doesn't bundle packages like php-mode, haskell-mode, eglot or
> lsp-mode, markdown-mode, etc.
I don't understand the relevance, please elaborate.
next prev parent reply other threads:[~2021-10-01 13:28 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
2021-10-01 13:15 ` Stefan Kangas
2021-10-01 13:28 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ee94euwe.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 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.