From: Eduardo Ochs <eduardoochs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Adam Porter <adam@alphapapa.net>, Po Lu <luangruo@yahoo.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
Richard Stallman <rms@gnu.org>,
Philip Kaludercic <philipk@posteo.net>,
"mardani29@yahoo.es" <mardani29@yahoo.es>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: apropos for packages [was: plz -> curl?]
Date: Tue, 17 May 2022 13:06:22 -0300 [thread overview]
Message-ID: <CADs++6haLAuZN0tmkd4zWP5t9okkBy8dH+K78MSabGJNyVweqA@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488F60294D2C75525A18C4DF3CE9@SJ0PR10MB5488.namprd10.prod.outlook.com>
On Tue, 17 May 2022 at 12:20, Drew Adams <drew.adams@oracle.com> wrote:
>
> > Is there an apropos-package command?
> > If not, maybe now is the time to write one.
>
> Good question.
>
> 1. There is `describe-package', `C-h P'.
>
> 2. It would be good to update `apropos-documentation',
> if this has not already been done, to include the
> doc of packages.
This looks like a good starting point to me... but find-eppp is
an eev-ism - `(find-eppp o)' displays a pretty-printed version of
o in a temporary buffer. What would normal people use instead of
the `find-eppp' here?
(find-eppp
(mapcar
(lambda (p)
(list (package-desc-name (cadr p))
(package-desc-summary (cadr p))))
package-archive-contents)
)
Cheers,
Eduardo Ochs
http://angg.twu.net/#eev
next prev parent reply other threads:[~2022-05-17 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 15:18 apropos for packages [was: plz -> curl?] Drew Adams
2022-05-17 16:06 ` Eduardo Ochs [this message]
2022-05-17 16:23 ` Drew Adams
2022-05-17 16:48 ` Eli Zaretskii
2022-05-17 18:04 ` [External] : " Drew Adams
2022-05-17 18:28 ` Eli Zaretskii
2022-05-25 20:47 ` Drew Adams
2022-05-18 22:19 ` Richard Stallman
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=CADs++6haLAuZN0tmkd4zWP5t9okkBy8dH+K78MSabGJNyVweqA@mail.gmail.com \
--to=eduardoochs@gmail.com \
--cc=adam@alphapapa.net \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=mardani29@yahoo.es \
--cc=philipk@posteo.net \
--cc=rms@gnu.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 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).