unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Rahguzar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	66676@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#66676: 29.1; Should some aspects of shr rendering be configurable
Date: Sun, 19 Nov 2023 12:12:08 +0100	[thread overview]
Message-ID: <87edgmt2me.fsf@zohomail.eu> (raw)
In-Reply-To: <87sf53aq6i.fsf@gmail.com>


Kévin Le Gouguec <kevin.legouguec@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





      reply	other threads:[~2023-11-19 11:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22  7:29 bug#66676: 29.1; Should some aspects of shr rendering be configurable Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-22  9:52 ` Eli Zaretskii
2023-10-22 10:26   ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 16:18     ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04  8:10       ` Eli Zaretskii
2023-11-04  9:06         ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 12:05         ` Kévin Le Gouguec
2023-11-18  8:59           ` Eli Zaretskii
2023-11-19 12:07             ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-22 20:14               ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-25 11:01                 ` Eli Zaretskii
2023-11-18 13:08           ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-18 18:09             ` Kévin Le Gouguec
2023-11-19 11:12               ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=87edgmt2me.fsf@zohomail.eu \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66676@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kevin.legouguec@gmail.com \
    --cc=larsi@gnus.org \
    --cc=rahguzar@zohomail.eu \
    /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).