unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Will Mengarini <seldon@eskimo.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Package "luwak"
Date: Mon, 05 Dec 2022 17:30:32 -0500	[thread overview]
Message-ID: <E1p2Jyq-0008E2-Li@fencepost.gnu.org> (raw)
In-Reply-To: <Y40qwo4xDBY0d93C@eskimo.com> (message from Will Mengarini on Sun, 4 Dec 2022 15:18:26 -0800)

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

  > The name "eww" is also unhelpful.  Perhaps
  > the merger should be under the name "lynx".

Does EWW work using lynx?  If so, that would be a good idea.  We would
replace two unhelpful package names with one name that would be
helpful and easy to remember.

If EWW does not work using lynx, then renaming it to `lynx' would be
misleading at one level.  We might rather make a different choice.

What other packages do we have for looking at web pages?  I see there
is `browse-url'.  Is that an alternative to EWW, or just a higherlevel
confugurable interface to EWW and other options?

Are there any more web-browsing packages that we should consider in
this planning?

-- 
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-12-05 22:30 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 [this message]
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=E1p2Jyq-0008E2-Li@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=seldon@eskimo.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).