From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rustand.lars@gmail.com, 68418@debbugs.gnu.org, salutis@me.com
Subject: bug#68418: refill-mode interferes with org-mode headlines
Date: Sat, 13 Jan 2024 19:33:55 +0000 [thread overview]
Message-ID: <87o7dpt4d8.fsf@localhost> (raw)
In-Reply-To: <83ply5f38w.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> We already agreed that fill-region-as-paragraph cannot use
> fill-paragraph-function, right? So what should
> fill-region-as-paragraph do in order to behave more correctly in Org
> buffers? IOW, what are the specific problems in
> fill-region-as-paragraph that break it in Org buffers? (I presume
> that use-hard-newlines is nil in these cases, so fill-paragraph is
> currently not relevant.)
`fill-region-as-paragraph' itself is not a problem.
The problem is that calling `fill-region-as-paragraph' directly does not
make sense in Org buffers - it will break the markup.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-01-13 19:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 20:18 bug#68418: refill-mode interferes with org-mode headlines Lars Rustand
2024-01-13 8:19 ` Eli Zaretskii
2024-01-13 9:01 ` Lars Rustand
2024-01-13 9:16 ` Eli Zaretskii
2024-01-27 8:55 ` Eli Zaretskii
2024-01-13 13:28 ` Ihor Radchenko
2024-01-13 13:43 ` Eli Zaretskii
2024-01-13 13:56 ` Ihor Radchenko
2024-01-13 15:13 ` Eli Zaretskii
2024-01-13 15:26 ` Ihor Radchenko
2024-01-13 15:57 ` Eli Zaretskii
2024-01-13 18:37 ` Ihor Radchenko
2024-01-13 19:00 ` Eli Zaretskii
2024-01-13 19:13 ` Ihor Radchenko
2024-01-13 19:21 ` Eli Zaretskii
2024-01-13 19:33 ` Ihor Radchenko [this message]
2024-01-13 19:57 ` Eli Zaretskii
2024-01-13 20:11 ` Ihor Radchenko
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=87o7dpt4d8.fsf@localhost \
--to=yantar92@posteo.net \
--cc=68418@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rustand.lars@gmail.com \
--cc=salutis@me.com \
/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).