From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 72485@debbugs.gnu.org
Subject: bug#72485: Support 'visual-wrap-prefix-mode' in SHR/EWW
Date: Sun, 18 Aug 2024 11:28:40 -0700 [thread overview]
Message-ID: <7fdfc885-3685-bc56-f3c7-bf7343711cc1@gmail.com> (raw)
In-Reply-To: <86zfp9ya2u.fsf@gnu.org>
On 8/18/2024 11:12 AM, Eli Zaretskii wrote:
> *** EWW now enables 'visual-wrap-prefix-mode' when 'shr-fill-text' is nil.
> By default, 'shr-fill-text' is t, and EWW fills the text according to
> the width of the window. If you customize 'shr-fill-text' to nil,
> EWW will now automatically turn on 'visual-wrap-prefix-mode' in
> addition to 'visual-line-mode', so that long lines are wrapped at
> word boundaries near window edge and the continuation lines are
> indented using prefixes computed from surrounding context.
That seems good to me, so I'll just use that as-is for Emacs 31. How
about this for the release branch?
*** New option 'shr-fill-text'.
When 'shr-fill-text' is non-nil (the default), SHR will fill the text
according to the width of the window. If you customize it to nil, SHR
will leave the text as-is; in that case, EWW will automatically enable
'visual-line-mode' when displaying a page so that long lines are
visually wrapped at word boundaries.
(If you think this makes the Emacs 31 NEWS entry partially redundant, I
can try to trim that one down to only discuss the new additions, but I
don't mind either way.)
next prev parent reply other threads:[~2024-08-18 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 3:47 bug#72485: Support 'visual-wrap-prefix-mode' in SHR/EWW Jim Porter
2024-08-17 8:55 ` Eli Zaretskii
2024-08-18 0:30 ` Jim Porter
2024-08-18 4:49 ` Eli Zaretskii
2024-08-18 6:13 ` Jim Porter
2024-08-18 9:20 ` Eli Zaretskii
2024-08-18 16:58 ` Jim Porter
2024-08-18 18:12 ` Eli Zaretskii
2024-08-18 18:28 ` Jim Porter [this message]
2024-08-18 18:53 ` Eli Zaretskii
2024-08-18 23:10 ` 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=7fdfc885-3685-bc56-f3c7-bf7343711cc1@gmail.com \
--to=jporterbugs@gmail.com \
--cc=72485@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).