From: Tassilo Horn <tsdh@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: bruce.connor.am@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Improving browsing and discoverability in the Packages Menu
Date: Tue, 21 Apr 2015 08:52:14 +0200 [thread overview]
Message-ID: <87lhhmgeht.fsf@gnu.org> (raw)
In-Reply-To: <ec32e410-867b-458d-84d1-e3dfce5e7ab9@default> (Drew Adams's message of "Mon, 20 Apr 2015 22:25:37 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
>> If it were intended by the package author, where is the problem of
>> adding
>> ;; byte-compile-warnings: (not unknown-keyword)
>> to the package's local variables section?
>
> So to some file written by someone somewhere somewhen, perhaps quite
> some time ago, you say: "All ya gotta do is jump through this leetle
> hoop here."
Yes, exactly. Because if it is available via ELPA, MELPA, or some other
package archive, then it seems to be actively maintained. And in the
very unlikely case that the author/maintainer insists on "modeline"
instead of "mode-line", she can jump through the little hoop.
BTW, an `unknown-keyword' warning was not really what I meant in my
previous reply. Of course, package.el cannot know all sensible
keywords, so it should work with any keyword. But in the case of
keywords that are likely just synonyms or typos of some commonly used
keyword (modeline vs. mode-line), it could suggest the commonly used one
for achieving a bit standardization.
>> And I'm pretty sure you won't see any occurrence of
>> ;; Keywords: modeline, electronic mail
>> ;; Package Keywords: mode-line, email
>> even if there was a new field.
>
> Sorry, I didn't catch your last point. Perhaps you mean to say that
> `Keywords' will disappear? All the kids will run to play in the new
> sandbox?
No, what I've meant to say is that when a maintainer adds the new
`Package Keywords' header duplicating the existing `Keywords' header and
then sees that byte-compilation suggests to use the more commonly used
"mode-line" and "email" instead of "modeline" and "electronic mail", why
should she change only `Package Keywords` accordingly and not
`Keywords', too? (Assuming that she agrees that "mode-line" and "email"
express what she intended to express, too.)
She doesn't know that there are some people that don't want `Keywords'
to be changed. Or should the warning say something like that?
The Package Keywords entry "modeline" is likely to mean "mode-line".
If you agree, change it accordingly but please let the Keywords
header as-is for the Olt Town's habitants peace of mind.
Bye,
Tassilo
next prev parent reply other threads:[~2015-04-21 6:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 22:38 Improving browsing and discoverability in the Packages Menu Artur Malabarba
2015-02-16 2:25 ` Stefan Monnier
2015-02-18 16:23 ` raman
2015-04-18 11:26 ` Ted Zlatanov
2015-04-18 13:25 ` Artur Malabarba
2015-04-18 13:25 ` Artur Malabarba
2015-04-18 21:11 ` raman
2015-04-18 23:05 ` Ted Zlatanov
2015-04-19 1:20 ` Alexis
2015-04-19 3:16 ` Stefan Monnier
2015-04-19 4:03 ` Alexis
2015-04-19 16:14 ` raman
2015-04-20 1:57 ` Stefan Monnier
2015-04-19 16:12 ` raman
2015-04-20 1:22 ` Ted Zlatanov
2015-04-20 9:02 ` Artur Malabarba
2015-04-20 15:18 ` raman
2015-04-20 15:23 ` Drew Adams
2015-04-21 0:20 ` raman
2015-04-21 1:07 ` Drew Adams
2015-04-19 2:59 ` Eric Abrahamsen
2015-04-19 14:58 ` Drew Adams
2015-04-20 8:38 ` Eric Abrahamsen
2015-04-20 9:26 ` Artur Malabarba
2015-04-20 10:17 ` Alexis
2015-04-20 11:30 ` Artur Malabarba
2015-04-20 14:32 ` Drew Adams
2015-04-20 17:32 ` Artur Malabarba
2015-04-20 18:17 ` Drew Adams
2015-04-20 19:49 ` Artur Malabarba
2015-04-20 20:30 ` Drew Adams
2015-04-21 4:05 ` Tassilo Horn
2015-04-21 5:25 ` Drew Adams
2015-04-21 6:52 ` Tassilo Horn [this message]
2015-04-21 9:04 ` Eric Abrahamsen
2015-04-21 15:44 ` Drew Adams
2015-04-20 14:03 ` Eric Abrahamsen
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=87lhhmgeht.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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).