bug#68254: EWW ‘readable’ by default

[Jim Porter]

On 1/5/2024 5:35 AM, Eli Zaretskii wrote:
> [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.

Here's a patch for this. It turns 'eww-readable' into a toggle (using 
the same semantics as minor modes), and also adds an option to prevent 
adding a new history entry for each call.

After this patch, you could set 'eww-readable-adds-to-history' to nil 
and add 'eww-readable' to 'eww-after-render-hook', and then everything 
should work ok. With those settings, you could then call 'eww-readable' 
to display the full page if needed.

(There might be some value in adding another new option that lets you 
specify a list of regexps to match pages that should start in readable 
mode; then it would be easy for users to enable that for 
"https://example\.com/.*"; or similar. We can do that later if there's 
any demand for it, though.)

0001-Allow-toggling-readable-mode-in-EWW.patch
Description: Text document