From: Alan Mackenzie <acm@muc.de>
To: Adam Porter <adam@alphapapa.net>
Cc: "Philip Kaludercic" <philipk@posteo.net>,
"Daniel Martín" <mardani29@yahoo.es>,
rms@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: plz
Date: Thu, 12 May 2022 13:54:40 +0000 [thread overview]
Message-ID: <Yn0RoC4nfqt9/tdR@ACM> (raw)
In-Reply-To: <104ffa6b-12ae-53df-e289-aba7d7200654@alphapapa.net>
Hello, Adam.
On Wed, May 11, 2022 at 14:29:22 -0500, Adam Porter wrote:
> On 5/11/22 13:55, Philip Kaludercic wrote:
> > Daniel Martín <mardani29@yahoo.es> writes:
> >> Adam Porter <adam@alphapapa.net> writes:
> >> [...], I think it's wise to rename the library to something
> >> more descriptive before people start writing packages using it. It
> >> will be much harder to rename the library later.
> > I would agree, but I know that Adam and I have different opinions on the
> > matter.
> I've often advocated for descriptive names when reviewing MELPA
> submissions, but I've also come to appreciate concise, distinctive
> names. In this case, as I wrote in the commentary, there are already
> packages named url.el, request.el, and http.el (the latter of which
> serves a different purpose altogether).
> And I think it doesn't matter here: if someone wonders what plz.el does,
> they can "C-h P plz RET" and find out. And if someone is looking for an
> HTTP library, they can "M-x list-packages RET / d http RET" and find some.
> The prefix "plz" is concise, which is valuable in code. And a bit of
> mild humor is...well, software can be very dry, and Lisp is supposed to
> be fun, so I like it. :) (Also, naming things is hard.)
Totally off topic here, but PLZ in German is the standard abbreviation
for Postleitzahl, or postcode in English. (I believe it's called a
zipcode in the USA.) Surely this isn't a bad name for something which
gets you something at a particular "place". :-)
> As to inclusion in core, as Eli said, that wouldn't be appropriate as
> long as it requires curl. As well, while I've been using it
> successfully for a couple of years now, and, as I wrote in the readme,
> it's generally useful for most HTTP needs, with regard to HTTP features
> it's far from complete. It needs to be used more widely and tested more
> thoroughly, and being on ELPA would be a good step toward that.
> Having said that, if it were to eventually mature to the point where it
> didn't require curl and were suitable for core, renaming it would be
> appropriate, and I think it wouldn't be a problem to do so then.
> Thanks for the feedback.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-05-12 13:54 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 16:51 [ELPA] New package: plz Adam Porter
2022-05-09 19:50 ` Philip Kaludercic
2022-05-09 21:08 ` Adam Porter
2022-05-10 11:58 ` Philip Kaludercic
2022-05-10 7:51 ` Adam Porter
2022-05-11 9:02 ` Richard Stallman
2022-05-11 10:19 ` Adam Porter
2022-05-11 13:42 ` Filipp Gunbin
2022-05-11 14:02 ` Adam Porter
2022-05-11 14:22 ` Daniel Martín
2022-05-11 15:51 ` Eli Zaretskii
2022-05-11 18:55 ` Philip Kaludercic
2022-05-11 19:29 ` Adam Porter
2022-05-12 13:06 ` Filipp Gunbin
2022-05-12 13:54 ` Alan Mackenzie [this message]
2022-05-12 15:23 ` Stefan Monnier
2022-05-14 23:58 ` Richard Stallman
2022-05-15 7:53 ` Adam Porter
2022-05-16 23:25 ` plz -> curl? Richard Stallman
2022-05-17 0:50 ` Po Lu
2022-05-17 2:13 ` Adam Porter
2022-05-17 2:37 ` Eli Zaretskii
2022-05-17 2:50 ` Po Lu
2022-05-17 10:13 ` Dmitry Gutov
2022-05-17 8:07 ` Philip Kaludercic
2022-05-17 22:58 ` Richard Stallman
2022-05-17 2:38 ` Eli Zaretskii
2022-05-17 3:05 ` Po Lu
2022-05-17 11:44 ` Eli Zaretskii
2022-05-17 11:46 ` Po Lu
2022-05-17 15:43 ` Eli Zaretskii
2022-05-17 19:15 ` Philip Kaludercic
2022-05-17 22:58 ` Richard Stallman
2022-05-17 6:43 ` Tassilo Horn
2022-05-17 8:17 ` Lars Ingebrigtsen
2022-05-17 10:12 ` Po Lu
2022-05-17 10:15 ` Adam Porter
2022-05-17 11:48 ` Po Lu
2022-05-17 15:38 ` Tassilo Horn
2022-05-18 0:46 ` Eric Abrahamsen
2022-05-17 12:15 ` Eli Zaretskii
2022-05-17 22:59 ` Richard Stallman
2022-05-17 22:58 ` Richard Stallman
2022-05-17 12:10 ` Stefan Monnier
2022-05-17 15:22 ` Roland Winkler
2022-05-17 22:59 ` Richard Stallman
2022-05-21 10:29 ` Jonas Bernoulli
2022-05-22 17:05 ` Juri Linkov
2022-05-22 23:01 ` Richard Stallman
2022-05-17 8:16 ` Alan Mackenzie
2022-05-17 22:59 ` Richard Stallman
2022-05-21 10:11 ` Jonas Bernoulli
2022-05-15 14:06 ` Wrong default-directory in shell buffer Matthias Meulien
2022-05-15 16:06 ` Stefan Monnier
2022-05-16 18:06 ` Matthias Meulien
2022-05-16 19:29 ` Matthias Meulien
2022-05-17 9:58 ` Visuwesh
2022-05-17 19:14 ` Matthias Meulien
2022-05-17 19:27 ` Lars Ingebrigtsen
2022-05-17 20:59 ` Matthias Meulien
2022-05-17 21:36 ` Lars Ingebrigtsen
2022-05-13 15:09 ` [ELPA] New package: plz Richard Stallman
2022-05-13 21:54 ` Adam Porter
2022-05-11 21:36 ` Stefan Monnier
2022-05-11 22:30 ` Adam Porter
2022-05-11 23:55 ` Stefan Monnier
2022-05-14 14:12 ` Richard Stallman
2022-05-14 14:23 ` Stefan Monnier
2022-05-16 23:26 ` Richard Stallman
2022-05-21 11:13 ` Jonas Bernoulli
2022-05-21 11:29 ` Eli Zaretskii
2022-05-21 18:16 ` Jonas Bernoulli
2022-05-21 14:51 ` Stefan Monnier
2022-05-21 18:10 ` Jonas Bernoulli
2022-05-21 20:29 ` Stefan Monnier
2022-05-22 23:02 ` Richard Stallman
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=Yn0RoC4nfqt9/tdR@ACM \
--to=acm@muc.de \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=philipk@posteo.net \
--cc=rms@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).