From: Daniel Mendler <mail@daniel-mendler.de>
To: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 66335@debbugs.gnu.org
Subject: bug#66335: 29.1.50; Additional known keywords for finder
Date: Wed, 4 Oct 2023 20:53:12 +0200 [thread overview]
Message-ID: <e443cd71-2641-46b6-a307-a1f1041c66bd@daniel-mendler.de> (raw)
In-Reply-To: <CADwFkmnY0Vg5CxwReiJoJpReGrFhL44B+vGTCUpnLMRV-+FZdg@mail.gmail.com>
On 10/4/23 20:43, Stefan Kangas wrote:
>>> I propose to add a few more commonly used keywords to finder.el. For
>>> example "tree-sitter" is used by all the newly introduced major modes.
>>> Besides that the following additional keywords might be useful and could
>>> be added to `finder-known-keywords':
>>>
>>> (accessibility . "Features improving accessibility")
>>> (completion . "Minibuffer and code completion")
>>> (network . "Features accessing the network")
>>> (theme . "Themes and styling")
>>> (tree-sitter . "Modes based Tree-Sitter")
>>
>> I think adding meaningful keywords is always welcome, the only problem
>> is to go over all the packages and add the new keywords to those which
>> need it.
>
> Daniel, would you like to propose a patch?
A patch to finder.el or to *all* packages? My proposal aims to add a few
keywords to finder.el, which seem to be used already, also across
ELPA/MELPA.
Besides that, the finder keyword list is not regenerated when installing
packages. This could be improved by calling `finder-compile-keywords',
taking the `finder-keywords-hash' and dumping it to some file which is
loaded by the init.el.
Daniel
next prev parent reply other threads:[~2023-10-04 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 10:20 bug#66335: 29.1.50; Additional known keywords for finder Daniel Mendler
2023-10-04 17:21 ` Eli Zaretskii
2023-10-04 18:43 ` Stefan Kangas
2023-10-04 18:53 ` Daniel Mendler [this message]
2023-10-04 20:33 ` Stefan Kangas
2023-10-05 5:34 ` Eli Zaretskii
2023-10-06 8:21 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=e443cd71-2641-46b6-a307-a1f1041c66bd@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=66335@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefankangas@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 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.