From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Adam Porter <adam@alphapapa.net>
Cc: Philip Kaludercic <philipk@posteo.net>,
"Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: ELPA: new package nano-agenda
Date: Mon, 18 Oct 2021 19:05:37 -0400 [thread overview]
Message-ID: <jwvfssyrl83.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAO_b3FVWH4DNZB6S1=0iUWf8JnUjb7qNU4gmXNQHF8yZJ-uMRw@mail.gmail.com> (Adam Porter's message of "Mon, 18 Oct 2021 17:50:32 -0500")
> Yes, I'd be glad to have ts.el in GNU ELPA.
That'd be nice.
> And I'd be glad to remove the dependency on s.el to facilitate that.
Yes, that'd be necessary before we can add it to GNU ELPA.
> The only potential issue that I can see is that it currently emits
> extra warnings at load time (or is it compile time? I forget...) on
> Emacs 28 due to more strict checking in the byte compiler.
That's fine (code doesn't have to be bug-free, luckily, otherwise not
only GNU ELPA would be empty, but Emacs wouldn't exist either).
>> What might be an issue is if the "ts-" namespace is considered to be
>> "too valuable", as was the issue with "s-" and "f-". The maintainers
>> would have to decide on that, I can only speculate.
two-letter (well, 3 if you count the dash) prefixes are fine, thanks
(we have loads of them).
Stefan
next prev parent reply other threads:[~2021-10-18 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 17:01 ELPA: new package nano-agenda Nicolas P. Rougier (inria)
2021-10-12 19:19 ` Philip Kaludercic
2021-10-12 19:29 ` Nicolas P. Rougier (inria)
2021-10-12 19:41 ` Philip Kaludercic
2021-10-18 22:50 ` Adam Porter
2021-10-18 23:05 ` Stefan Monnier [this message]
2021-10-19 11:55 ` Philip Kaludercic
2021-10-19 12:07 ` Stefan Kangas
2021-10-19 12:24 ` Philip Kaludercic
2021-10-21 14:28 ` Philip Kaludercic
2021-10-19 6:39 ` Joost Kremers
2021-10-19 10:19 ` Nicolas P. Rougier (inria)
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=jwvfssyrl83.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=nicolas.rougier@inria.fr \
--cc=philipk@posteo.net \
/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).