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: Sat, 17 Aug 2024 23:13:00 -0700 [thread overview]
Message-ID: <671bd15e-35f4-caca-d99c-ef6e92d6a588@gmail.com> (raw)
In-Reply-To: <868qwu1llq.fsf@gnu.org>
On 8/17/2024 9:49 PM, Eli Zaretskii wrote:
> I'm not sure many users know about shr-fill-text, including that its
> default is non-nil. So I think this NEWS entry should say something
> about that, otherwise this text might cause incorrect user
> expectations.
How does this sound?
----------------------------------------
*** EWW now enables 'visual-wrap-prefix-mode' when 'shr-fill-text' is nil.
Previously, when 'shr-fill-text' was nil, EWW would use
'visual-line-mode' to wrap paragraphs instead of inserting newline
characters. Now, EWW additionally enables 'visual-wrap-prefix-mode' in
this case. This improves the display of multiline, indented text, such
as block quotes or (un)ordered lists.
----------------------------------------
I also notice that 'shr-fill-text' is new in Emacs 30, but doesn't have
a NEWS entry in that release. Should I add a mention of it to the Emacs
30 NEWS as well? (I don't see any harm in reiterating what
'shr-fill-text' does in the Emacs 31 NEWS as well though.)
next prev parent reply other threads:[~2024-08-18 6:13 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 [this message]
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
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=671bd15e-35f4-caca-d99c-ef6e92d6a588@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).