From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Merten <stefan@merten-home.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
74785@debbugs.gnu.org, Richard Brooksby <rb@ravenbrook.com>
Subject: bug#74785: 27.1; Fill-paragraph in RST mode does not respect line blocks
Date: Mon, 16 Dec 2024 21:53:31 -0500 [thread overview]
Message-ID: <jwvh673m3md.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <376758.1734386711@eskebo> (Stefan Merten's message of "Mon, 16 Dec 2024 23:05:11 +0100")
>>> | This is the all the first line
>>> of output even though it's two lines
>>> of input.
>>> | This is second line in the output.
>>> | And this is the third.
[...]
>> Stefan and Stefan, any ideas or suggestions?
[ With all those Stefans around I feel like nothing can stop us. ]
I think we "just" need to:
- set `paragraph-start` to match a line with a leading `|`.
- set `adaptive-fill-regexp` to match this leading `|`.
If the `paragraph-start` setting makes paragraph navigation inconvenient
(too fine-grained), we could try and set
`fill-forward-paragraph-function` to a function which let-binds
`paragraph-start` around a call to `forward-paragraph`.
Stefan
next prev parent reply other threads:[~2024-12-17 2:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:37 bug#74785: 27.1; Fill-paragraph in RST mode does not respect line blocks Richard Brooksby
2024-12-14 10:22 ` Eli Zaretskii
2024-12-16 22:05 ` Stefan Merten
2024-12-17 2:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-17 6:05 ` James Cloos
2024-12-17 12:51 ` Eli Zaretskii
2024-12-17 14:49 ` James Cloos
2024-12-17 15:11 ` Eli Zaretskii
2024-12-17 15:34 ` Richard Brooksby
2024-12-17 15:41 ` Eli Zaretskii
2024-12-17 17:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-17 12:25 ` Eli Zaretskii
2024-12-17 17:12 ` Stefan Monnier 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=jwvh673m3md.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=74785@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rb@ravenbrook.com \
--cc=stefan@merten-home.de \
/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).