From: Adam Porter <adam@alphapapa.net>
To: jporterbugs@gmail.com
Cc: 68254@debbugs.gnu.org, eliz@gnu.org, yvv0@proton.me
Subject: bug#68254: EWW ‘readable’ by default
Date: Sun, 17 Mar 2024 23:32:33 -0500 [thread overview]
Message-ID: <67bf26f6-382e-4065-8e02-b6433fe78b76@alphapapa.net> (raw)
In-Reply-To: <6ee278b0-1511-cfd9-7695-7e019d879f7b@gmail.com>
Hi all,
I'm not sure it would be a good idea to enable eww-readable by default.
IME eww-readable is not reliably effective enough to be used by default.
I think that if it were, too many users would find that EWW would
produce unusable results by default, and they'd likely blame EWW itself
rather than eww-readable, being unaware that eww-readable were even
involved.
I wish this weren't the case, but the modern Web is too, er, modern, I'm
afraid.
I like Jim's idea of having an option of URL-matching regexps that
automatically activate eww-readable. That does sound useful.
My two cents.
--Adam
next prev parent reply other threads:[~2024-03-18 4:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 7:35 bug#68254: EWW ‘readable’ by default Navajeeth via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-05 11:52 ` Eli Zaretskii
[not found] ` <poNSnv1DQ7L71-FirbCx9nuQ8gqLlPGTIjDYk2pKo2_H3BPuJArYQ2ziQ4pyADSxHCY5cU40D6MUzRqBAZE3pEcFmnzFPD49xunpLyh1UqI=@proton.me>
2024-01-05 13:35 ` Eli Zaretskii
2024-03-17 19:24 ` Jim Porter
2024-03-18 4:32 ` Adam Porter [this message]
2024-03-18 5:17 ` Navajeeth via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-18 5:44 ` Jim Porter
2024-03-18 5:18 ` Jim Porter
2024-03-18 12:37 ` Eli Zaretskii
2024-03-19 0:00 ` Jim Porter
2024-03-21 10:51 ` Eli Zaretskii
2024-03-22 5:46 ` Jim Porter
2024-03-23 7:48 ` Eli Zaretskii
2024-03-23 17:26 ` Jim Porter
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=67bf26f6-382e-4065-8e02-b6433fe78b76@alphapapa.net \
--to=adam@alphapapa.net \
--cc=68254@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=yvv0@proton.me \
/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).