From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>, Juri Linkov <juri@jurta.org>
Cc: 10280@debbugs.gnu.org, Jari Aalto <jari.aalto@cante.net>
Subject: bug#10280: ruby-mode.el - Unknown finder.el keyword: ruby
Date: Sun, 11 Aug 2019 18:03:19 -0700 (PDT) [thread overview]
Message-ID: <48f25e91-a16d-4210-9c11-943b6018110b@default> (raw)
In-Reply-To: <CADwFkmk7K3kQ1E8j_Ph3LSq-QVidJOW3rzKWpLim1aL9h4tteg@mail.gmail.com>
> >> ;; Keywords: languages ruby
> >>
> >> However word "ruby" is not in list returned by M-x finder-list-
> >> keywords. Perhaps finder-list-keywords or ruby.el should be updated.
> >
> > Free-form user-defined keywords are allowed since the list of
> > keywords is open-ended. So this is rather a shortcoming of
> > `finder-list-keywords'
No, it's not a shortcoming. It's open-ended by design,
AFAIK, and that's good.
> > that doesn't yet list all keywords beyond a few of "official" ones.
And it shouldn't, IMO. list `finder-known-keywords'
should remain something defined by Emacs.
On the other hand, `finder.el' could be enhanced
to provide such a feature as an _option_. It
could have a user option whose value is a list
of additional keywords to recognize.
That's the approach we take with Dired guessing
shell-command associations. We have a non-option
variable, `dired-guess-shell-alist-default', which
is defines the default associations, and we have
a user option, `dired-guess-shell-alist-user',
which is prepended to the default list.
That would let users control the behavior of
`finder-list-keywords'. After all, that's a
command - it's for users.
> Do we really want to change finder-list-keywords to list all keywords?
> (For some definition of "all".)
No, we don't; that is, I don't.
Field `Keywords' is _not_ just for `finder.el'.
It's for anything a library writer (or user) wants
it to be for.
(I believe it predates `finder.el', but I'm not sure
of that.)
> Wouldn't that make the menu much harder to navigate?
Yes. If we want to let users choose that, and choose
how much harder (which and how many extra keywords),
that's fine, however.
next prev parent reply other threads:[~2019-08-12 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 17:24 bug#10280: ruby-mode.el - Unknown finder.el keyword: ruby Jari Aalto
2011-12-15 21:35 ` Juri Linkov
2019-08-12 0:32 ` Stefan Kangas
2019-08-12 1:03 ` Drew Adams [this message]
2019-08-12 21:27 ` Juri Linkov
2019-08-13 7:02 ` Stefan Kangas
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=48f25e91-a16d-4210-9c11-943b6018110b@default \
--to=drew.adams@oracle.com \
--cc=10280@debbugs.gnu.org \
--cc=jari.aalto@cante.net \
--cc=juri@jurta.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).