unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Richard Stallman <rms@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  emacs-devel@gnu.org
Subject: Re: Package "luwak"
Date: Mon, 12 Dec 2022 22:42:54 +0000	[thread overview]
Message-ID: <87k02ws0pd.fsf@posteo.net> (raw)
In-Reply-To: <E1p4r8o-00033B-9D@fencepost.gnu.org> (Richard Stallman's message of "Mon, 12 Dec 2022 17:19:18 -0500")

Richard Stallman <rms@gnu.org> writes:

> [[[ 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. ]]]
>
>   > > Does anyone have a better name to suggest?
>
>   > Luwak sounds perfect to me.
>
> I think you are not being serious.  If you are, can you explain why
> you consider "luwak" better than "lynx"?

Honestly, neither of the two is that useful for a modern user
(ie. someone who hasn't investigated text-mode web browsers).  I still
think of the wild cat...  That being said, the discussion has been had
over and over again, and it always results in more or less the same
people stating more or less the same preferences, which is a waste of
time because it is entirely unproductive.

If this is to be resolved in the long term, I think a naming guideline
or recommendations (for ELPA) should be written down.  What are a few
good examples everyone can agree on, what are a few bad examples, and
what makes them bad or good.  What attributes does a good name have
(e.g. easy to remember, easy to write, unique, leaning on convention and
experience, etc.).



  reply	other threads:[~2022-12-12 22:42 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
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 [this message]
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=87k02ws0pd.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).