From: "Alfred M. Szmidt" <ams@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: rms@gnu.org, philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: [External] : Re: Package "luwak"
Date: Fri, 16 Dec 2022 13:52:01 -0500 [thread overview]
Message-ID: <E1p6FoP-0003ev-77@fencepost.gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488D7A0731662C7BDAD9E9AF3E69@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Fri, 16 Dec 2022 17:31:57 +0000)
Good initiative. The point truly is _discoverability_.
Thanks, but this is only useful someone picks up the taks, and does
something ... ideas are easy.
We might imagine some semi-automatic way (suggestions for a
maintainer) of coming up with relevant keywords, to help make
the job of adding and maintaining `Keywords' easier and more
fruitful.
Back in the day, we (the GNU nitpicker gang --
https://cvs.savannah.gnu.org/viewvc/womb/gnits/gnits.texi?view=log)
had a glossary of sorts, with tables of commonly used options, and
what nots. It wasn't semi-automatic, very much manual, and even so
more so that hard to know about it.
Maybe this could be automated somewhat, a M-x identify-package like
command that asks the user stuff, and tries to match things against
some file.
Ofcourse, these are just random ideas, someone would have to implement
something ... alas I'm out of general time to do this.
next prev parent reply other threads:[~2022-12-16 18:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 23:51 Package "luwak" Richard Stallman
2022-12-01 0:52 ` Stefan Monnier
2022-12-02 22:51 ` Richard Stallman
2022-12-03 2:49 ` T.V Raman
2022-12-11 4:04 ` Yuchen Pei
2022-12-04 23:18 ` Will Mengarini
2022-12-05 4:25 ` Jean Louis
2022-12-05 22:30 ` Richard Stallman
2022-12-06 9:05 ` Philip Kaludercic
2022-12-06 22:37 ` Richard Stallman
2022-12-07 3:33 ` Eli Zaretskii
2022-12-07 7:11 ` Philip Kaludercic
2022-12-07 8:44 ` Andreas Schwab
2022-12-01 3:54 ` North Year
2022-12-11 3:54 ` Yuchen Pei
2022-12-11 23:34 ` Richard Stallman
2022-12-11 13:07 ` Yuchen Pei
2022-12-12 22:19 ` Richard Stallman
2022-12-11 14:29 ` Stefan Monnier
2022-12-11 18:03 ` Tim Cross
2022-12-12 22:19 ` Richard Stallman
2022-12-12 22:42 ` Philip Kaludercic
2022-12-13 23:58 ` Richard Stallman
2022-12-14 21:34 ` Philip Kaludercic
2022-12-14 21:41 ` [External] : " Drew Adams
2022-12-16 3:35 ` Richard Stallman
2022-12-16 15:33 ` Alfred M. Szmidt
2022-12-16 17:31 ` [External] : " Drew Adams
2022-12-16 18:52 ` Alfred M. Szmidt [this message]
2022-12-18 3:21 ` Richard Stallman
2022-12-16 11:05 ` Jean Louis
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=E1p6FoP-0003ev-77@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--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).