From: Ted Zlatanov <tzz@lifelogs.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 16735@debbugs.gnu.org
Subject: bug#16735: Not very useful "Keywords:" headers in some elpa packages
Date: Thu, 13 Feb 2014 13:21:16 -0500 [thread overview]
Message-ID: <87fvnmg9gj.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <oqwqgyc2cf.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 13 Feb 2014 13:08:32 -0500, Thu, 13 Feb 2014 13:05:22 -0500")
On Thu, 13 Feb 2014 13:08:32 -0500 Glenn Morris <rgm@gnu.org> wrote:
GM> Ted Zlatanov wrote:
>> Keywords is supposed to match the finder keywords.
GM> Is it? Exclusively?
GM> I used to think that, but I don't even know any more...
GM> So many people use it for random "here's a list of any word I could
GM> think of that is even vaguely related to this file".
I know, so I'm saying let's give them a new "Tags" header for that
purpose and gently encourage them to start using it.
>> Authors want a way to tag their packages with arbitrary keywords =
>> tags.
GM> Calendar uses "Human-Keywords" for that, but no-one else does AFAICS.
GM> IMO it is a shame "Keywords" was not called "Finder-Keywords" from the
GM> start, if that is really what it was supposed to be.
Yes, I agree.
GM> Anyway, all I was hoping to get from this bug report is that Someone
GM> would add the relevant finder keywords (languages, etc) to elpa.gnu.org
GM> packages that lack them.
I can do it, but in the process would like to start using Tags. Then we
have something to offer the authors so their intended tags (which
presumably are valuable) are not lost.
On Thu, 13 Feb 2014 13:05:22 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Keywords is supposed to match the finder keywords.
SM> No, they don't have to. But it's a good idea if they do.
Right.
SM> And same would hold for "Tag".
Why should it? It would be a new header, intended for arbitrary
strings, with no baggage. IOW you'd see
Keywords: language
Tags: mustache,handlebars
Does that make sense?
Ted
next prev parent reply other threads:[~2014-02-13 18:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 2:05 bug#16735: Not very useful "Keywords:" headers in some elpa packages Glenn Morris
2014-02-13 14:08 ` Ted Zlatanov
2014-02-13 16:00 ` Stefan Monnier
2014-02-13 17:01 ` Ted Zlatanov
2014-02-13 18:05 ` Stefan Monnier
2014-02-13 18:08 ` Glenn Morris
2014-02-13 18:16 ` Glenn Morris
2014-02-13 18:21 ` Ted Zlatanov [this message]
2014-02-13 19:12 ` Stefan Monnier
2014-02-13 19:37 ` Glenn Morris
2014-02-13 19:47 ` Drew Adams
2014-02-13 21:32 ` Ted Zlatanov
2014-02-14 1:50 ` Stefan Monnier
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=87fvnmg9gj.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=16735@debbugs.gnu.org \
--cc=rgm@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).