From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rahguzar@zohomail.eu, Lars Ingebrigtsen <larsi@gnus.org>,
66676@debbugs.gnu.org
Subject: bug#66676: 29.1; Should some aspects of shr rendering be configurable
Date: Sat, 04 Nov 2023 13:05:25 +0100 [thread overview]
Message-ID: <87wmuxoha2.fsf@gmail.com> (raw)
In-Reply-To: <83lebe547t.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Nov 2023 10:10:14 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Lars, anybody else? Any comments to these changes?
As an occasional user of shr (mainly when viewing HTML parts in Gnus)
who frequently messes with window width and face height, I'm very much
interested in better visual-line-mode integration. Also intrigued by
outline-mode support. So closely following this thread, and
enthusiastically thanking Rahguzar for tackling this 👏
Don't know if I have anything insightful to say re. the patches. Idly
wondering if '(null shr-fill-text) ⇒ (visual-line-mode)' is the right
control flow; e.g. maybe
(a) shr-fill-text could be set to 'visual as a more explicit hint for
major modes, or
(b) major modes should grow new user options: e.g. eww-wrap-method ∈
{fill, visual}; 'visual would tell modes to set shr-fill-text to nil &
enable visual-line-mode.
There are already plenty of user knobs at the shr level though, so maybe
no need to overthink this.
next prev parent reply other threads:[~2023-11-04 12:05 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 [this message]
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
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=87wmuxoha2.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=66676@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).