From: Eli Zaretskii <eliz@gnu.org>
To: Navajeeth <yvv0@proton.me>
Cc: 68254@debbugs.gnu.org
Subject: bug#68254: EWW ‘readable’ by default
Date: Fri, 05 Jan 2024 15:35:45 +0200 [thread overview]
Message-ID: <83frzbvr66.fsf@gnu.org> (raw)
In-Reply-To: <poNSnv1DQ7L71-FirbCx9nuQ8gqLlPGTIjDYk2pKo2_H3BPuJArYQ2ziQ4pyADSxHCY5cU40D6MUzRqBAZE3pEcFmnzFPD49xunpLyh1UqI=@proton.me> (message from Navajeeth on Fri, 05 Jan 2024 12:08:29 +0000)
[Please use Reply All to reply, so that the bug tracker is CC'ed.]
> Date: Fri, 05 Jan 2024 12:08:29 +0000
> From: Navajeeth <yvv0@proton.me>
>
> I’ve tried that method. While at first it appears to work how I want, it’s sub-optimal because it clutters
> your history with two version of every webpage you open: one the full non-readable version and then
> the readable version generated by the after-render-hook. Going back in the history is a chore,
> you need to press ‘l’ twice to go back one webpage.
>
> I used to tolerate it for a while, but now I feel that there could be a better way.
next prev parent reply other threads:[~2024-01-05 13:35 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 [this message]
2024-03-17 19:24 ` Jim Porter
2024-03-18 4:32 ` Adam Porter
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=83frzbvr66.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68254@debbugs.gnu.org \
--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).