unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: me@eshelyaron.com, emacs-devel@gnu.org, jan@swi-prolog.org
Subject: Re: [NonGNU ELPA] New package: sweep
Date: Thu, 29 Sep 2022 22:36:06 -0400	[thread overview]
Message-ID: <E1oe5sk-0000SJ-4X@fencepost.gnu.org> (raw)
In-Reply-To: <86o7v0pvla.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 27 Sep 2022 21:47:21 +0300)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > May I suggest using a name which is more descriptive than "Sweep"?
  > > A person who doesn't already know that it has to do with SWI-Prolog
  > > would never guess that.

  > Isn't "sweep" pronounced [swi:p]?

Yes, but that sound would never have led me to think of "SWI" or "Prolog"
if I had not already been informed.

We call Emacs the "self-documenting" text editor.  But packages are
not effectively self-documenting if their names don't give you at
least a glimmer of an idea of whether they are worth your finding out
more about.

Calling this package "SWEEP", pure and simple, would be a form of
"inside joke".  If you use a "SWEEP" package with SWI-Prolog, you
would see the relationship of names, and might find it amusing.  For
everyone else, it would be a confusing disguise for the package.

The change we seem to have decided will make this SWI Prolog package
somewhat discoverable.  But we have many other package names that are
unhelpful, such as eww, or so clever that they mislead, such as
company.

It's fine for a package name to be clever, but the first priority in
choosing the name should be to make the package discoverable.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2022-09-30  2:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 10:22 [NonGNU ELPA] New package: sweep Eshel Yaron
2022-09-26 17:41 ` Stefan Monnier
2022-09-27 15:19   ` Eshel Yaron
2022-09-30  2:36     ` Richard Stallman
2022-09-27 16:17 ` Richard Stallman
2022-09-27 18:47   ` Juri Linkov
2022-09-28  5:40     ` Andrea G. Monaco
2022-09-30  2:36     ` Richard Stallman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-26 11:29 Eshel Yaron
2022-09-26 19:32 ` Philip Kaludercic
2022-09-27 16:32   ` Eshel Yaron
2022-09-27 17:46     ` Philip Kaludercic
2022-09-28  6:46       ` Eshel Yaron
2022-09-28  7:27         ` Philip Kaludercic
2022-09-28 17:49           ` Juri Linkov
2022-09-28 18:41             ` Eli Zaretskii
2022-09-28 18:56             ` Philip Kaludercic
2022-09-30  2:38             ` Richard Stallman
2022-09-30  8:20             ` Stefan Kangas
2022-09-30  9:45               ` Robert Pluim
2022-09-29  2:59         ` Richard Stallman
2022-09-27 18:49     ` Stefan Monnier
2022-09-28  7:15       ` Eshel Yaron
2022-09-29  3:02     ` Richard Stallman
2022-09-29  5:04       ` Eshel Yaron
2022-09-29  6:17       ` Eli Zaretskii

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=E1oe5sk-0000SJ-4X@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan@swi-prolog.org \
    --cc=juri@linkov.net \
    --cc=me@eshelyaron.com \
    /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).