GNU bug report logs - #66676
29.1; Should some aspects of shr rendering be configurable

Previous Next

Full log

Message #37 received at 66676 <at> debbugs.gnu.org (full text, mbox):

From: Rahguzar <rahguzar <at> zohomail.eu>
To: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 66676 <at> debbugs.gnu.org,
 Lars Ingebrigtsen <larsi <at> gnus.org>
Subject: Re: bug#66676: 29.1; Should some aspects of shr rendering be
 configurable
Date: Sun, 19 Nov 2023 12:12:08 +0100

Kévin Le Gouguec <kevin.legouguec <at> gmail.com> writes:

> Gotcha.  Not sure why I have such a knee-jerk response to automating
> visual-line-mode activation.
>
> OT1H part of me likes your idea of not doing anything and letting users
> add visual-line-mode to eww-after-render-hook: it's explicit, it's less
> work for folks who would prefer to keep it off;

Turning on a minor mode from a hook is easier than turning it off so
that is one reason for preferring to not activate them. I think in
this case I think people want to not fill text and also not turn on
visual-line-mode should be rare enough that we should do it. But I don't
have very strong opinion on this.

> OTOH, can't quite picture anyone actually preferring that.  I guess by
> default, truncate-lines being nil, they would get some sort of
> "reflowing"…
>
> Tentative bottomline: it's fine as-is really 👍 The knobs are all there;
> I don't have an alternative that I strongly believe in.

Rahguzar

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.