unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: Package "luwak"
Date: Wed, 30 Nov 2022 18:51:03 -0500	[thread overview]
Message-ID: <E1p0Wr1-0008Rc-Sl@fencepost.gnu.org> (raw)

[[[ 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. ]]]

We just added a package with the name "luwak".  It browses using lynx.

The name "lynx" is somewhat helpful because it refers in an unmissable
way to the links that make the WWW better than ftp.

By contrast, the name "luwak" is unhelpful.  Wikipedia says "luwak" is
a species of civet; civets are not cats, but fairly close to cats.  If
you know this, it might help you remember "luwak" when you think of
"lynx".  But that relationship is remote and strained.  And it won't
help people who might find luwak useful find out about it.

Let's change the package name now to something that will help users
find out about it and use it.

My suggestion for the name is `lynx'.  That name fits it, since it is
an interface to lynx.  And anyone who knows about `lynx' will guess
what it does.

Does anyone have a better name to suggest?

-- 
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)





             reply	other threads:[~2022-11-30 23:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 23:51 Richard Stallman [this message]
2022-12-01  0:52 ` Package "luwak" 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
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=E1p0Wr1-0008Rc-Sl@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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).