unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 09:58:07 -0700	[thread overview]
Message-ID: <3a549122-156c-2993-34b0-2c4b071e8b38@gmail.com> (raw)
In-Reply-To: <861q2m192q.fsf@gnu.org>

On 8/18/2024 2:20 AM, Eli Zaretskii wrote:
> It still doesn't say that shr-fill-text is non-nil by default.
> 
>> 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?
> 
> Yes, please do.

How about this?

---------- For Emacs 30 ----------


*** New option 'shr-fill-text'.
When non-nil (the default), SHR will insert newlines in text to wrap it.
If customized to nil, SHR will leave the text as-is; in that case, EWW
will automatically enable 'visual-line-mode' to visually wrap the text
when displaying a page.


---------- For Emacs 31 ----------


*** EWW now enables 'visual-wrap-prefix-mode' when 'shr-fill-text' is nil.
When 'shr-fill-text' is customized to nil, EWW now enables
'visual-wrap-prefix-mode' when rendering in addition to
'visual-line-mode'.  This improves the display of multiline, indented
text, such as block quotes or (un)ordered lists.





  reply	other threads:[~2024-08-18 16:58 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 [this message]
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=3a549122-156c-2993-34b0-2c4b071e8b38@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).