From: Adam Porter <adam@alphapapa.net>
To: Po Lu <luangruo@yahoo.com>
Cc: Richard Stallman <rms@gnu.org>,
Philip Kaludercic <philipk@posteo.net>,
mardani29@yahoo.es, emacs-devel <emacs-devel@gnu.org>
Subject: Re: plz -> curl?
Date: Mon, 16 May 2022 21:13:51 -0500 [thread overview]
Message-ID: <CAO_b3FVwhgz9V1c+rF885_WZTcYYyLdvmJg3iKwi=VLAbA0HnA@mail.gmail.com> (raw)
In-Reply-To: <87o7zxnfsg.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2695 bytes --]
On Mon, May 16, 2022, 19:50 Po Lu <luangruo@yahoo.com> wrote:
> Richard Stallman <rms@gnu.org> writes:
>
> > We have arrived at a deep and fundamental disagreement about what it
> > means to make a program clear. I have pointed out that the name "plz"
> > gives no information about what the package does. It is totally
> > unhelpful.
> >
> > You contend that an arbitrary and unhelpful name is just as good as a
> > helpful name.
No, that is not my contention at all. I tried to explain my position as
clearly as I could in my last messages.
The argument is that we have commands to do searches
> > from the name to its purpose and from words in its purpose to the
> > name.
> >
> > Those commands are helpful, but using them is laborious by comparison
> > woth the simple verbalconnection.
> >
> > For the packages feature, I am a beginner. I don't know those
> > commands. I will learn these commands if I start using packages more,
> > but there will always be many users who are beginners in this.
>
Users who don't know how to use the package system will not be installing
the package in the first place.
>
> > Whenever we add a new package, we should consider whether to change
> > its name first. But plz has not been installed for long. Giving it a
> > clear, meaningful name now won't cause any pain.
>
> I agree completely. There are many unhelpful package names, such as
> "corfu", "cape", "eglot", "marginalia" and "mcd". At least eglot could
> be renamed "lsp-client", which tells the user exactly what it does.
>
Those packages have distinctive identities to those who use them. Giving
them generic names does not help the user remember them; it has the
opposite effect.
>
> > A clear meaningful name does not have to be long. Someone suggested
> > `curl' -- meaningful, and quite short.
As I said, I don't want to use that name, because it implies more
comprehensive support for curl than I intend to provide in the library. As
well, there are other packages that provide a front end to curl.
Perhaps `curl-url' would be
> > even more helpful, to the many who who don't use curl -- and it is
> > still short.
>
Thanks, but no.
> If no one has a better idea, let's rename it that way now.
>
> curl is already taken. `curl-url' would work, but so would
> `curl-http-client', which I think is relatively more meaningful.
>
As I've said, long, purely descriptive package names like that are less
useful in the long run, as well as simply being too long.
At this time, I don't intend to rename the library. Were it to be proposed
for merging into core someday, that would be different--but as has been
said, that won't be the case anytime soon, if ever.
>
[-- Attachment #2: Type: text/html, Size: 4786 bytes --]
next prev parent reply other threads:[~2022-05-17 2:13 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
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 [this message]
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='CAO_b3FVwhgz9V1c+rF885_WZTcYYyLdvmJg3iKwi=VLAbA0HnA@mail.gmail.com' \
--to=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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).