From: Richard Stallman <rms@gnu.org>
To: Yuchen Pei <id@ypei.org>
Cc: emacs-devel@gnu.org
Subject: Re: Package "luwak"
Date: Sun, 11 Dec 2022 18:34:44 -0500 [thread overview]
Message-ID: <E1p4VqG-0000qj-Cq@fencepost.gnu.org> (raw)
In-Reply-To: <87v8mifvcx.fsf@ypei.org> (message from Yuchen Pei on Sun, 11 Dec 2022 14:54:38 +1100)
[[[ 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. ]]]
> > lynx dump -> feline excretion -> Kopi Luwak
> Judging from your talk at EmacsConf, I guess you would still prefer a
> different name because this would still fall under word play.
I like wordplay in general, but this wordplay is so obscure that no one
will get the joke, so it isn't very funny.
For names of packages, the priority is to help users find ahwt is
useful to them. "Luwak" is no good for that, so we should not use
that name. If we want this ackage in Emacs, we should rename it to a
name that will help users find it and remember it.
That dosn't mean we can't keep this wordplay at all.
We could say, somewhere in the package description, that
This package was originally called "luwak", making a juke
lynx dump -> feline excretion -> Kopi Luwak
That would not interfere with higher priorities such as
discocerability and memorability.
But I think that it won't be sufficient to enable most Emacs users to
get the joke. That would require some more explanation. But there's
no harm in adding more explanation.
--
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)
next prev parent reply other threads:[~2022-12-11 23:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 23:51 Package "luwak" Richard Stallman
2022-12-01 0:52 ` Stefan Monnier
2022-12-02 22:51 ` Richard Stallman
2022-12-03 2:49 ` T.V Raman
2022-12-11 4:04 ` Yuchen Pei
2022-12-04 23:18 ` Will Mengarini
2022-12-05 4:25 ` Jean Louis
2022-12-05 22:30 ` Richard Stallman
2022-12-06 9:05 ` Philip Kaludercic
2022-12-06 22:37 ` Richard Stallman
2022-12-07 3:33 ` Eli Zaretskii
2022-12-07 7:11 ` Philip Kaludercic
2022-12-07 8:44 ` Andreas Schwab
2022-12-01 3:54 ` North Year
2022-12-11 3:54 ` Yuchen Pei
2022-12-11 23:34 ` Richard Stallman [this message]
2022-12-11 13:07 ` Yuchen Pei
2022-12-12 22:19 ` Richard Stallman
2022-12-11 14:29 ` Stefan Monnier
2022-12-11 18:03 ` Tim Cross
2022-12-12 22:19 ` Richard Stallman
2022-12-12 22:42 ` Philip Kaludercic
2022-12-13 23:58 ` Richard Stallman
2022-12-14 21:34 ` Philip Kaludercic
2022-12-14 21:41 ` [External] : " Drew Adams
2022-12-16 3:35 ` Richard Stallman
2022-12-16 15:33 ` Alfred M. Szmidt
2022-12-16 17:31 ` [External] : " Drew Adams
2022-12-16 18:52 ` Alfred M. Szmidt
2022-12-18 3:21 ` Richard Stallman
2022-12-16 11:05 ` Jean Louis
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=E1p4VqG-0000qj-Cq@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=id@ypei.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).