emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Beshara <m@mfa.pw>
To: emacs-orgmode@gnu.org
Subject: [BUG] org-fill-paragraph doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt/Code/emacs/lisp/org/)]
Date: Sun, 25 Sep 2022 09:39:59 +1000	[thread overview]
Message-ID: <87o7v4iawb.fsf@mfa.pw> (raw)

‘org-fill-paragraph’ does not correctly handle ^L characters 
(a.k.a. form feed, C-q C-l).  It should treat them as paragraph 
separating whitespace, but instead treats them as any other 
character which would appear in normal text.  Here is an example 
to demonstrate the current behaviour:

abc def
ghi jkl

In org-mode, with point at the beginning or the end of the first 
or last line, doing ‘org-fill-paragraph’ (M-q) should do nothing, 
because the lines are already shorter than the fill-column.  What 
really happens is that I end up with one line which looks like:

abc def ^L def ghi

In text-mode, ‘fill-paragraph’ does handle ^L characters 
correctly, and pressing M-q anywhere in the first example results 
in no change being made to the buffer.

Emacs  : GNU Emacs 29.0.50 (build 2, x86_64-pc-linux-gnu, X 
toolkit, cairo version 1.17.6)
 of 2022-08-27
Package: Org mode version 9.5.4 (release_9.5.4-19-g4dff42 @ 

             reply	other threads:[~2022-09-25 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 23:39 Matt Beshara [this message]
2022-09-26 11:39 ` Should page break (^L) work as paragraph element separator and be included into Org syntax? (was: [BUG] org-fill-paragraph doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt/Code/emacs/lisp/org/)]) Ihor Radchenko
2022-09-26 15:10   ` Matt Beshara
2022-09-27  6:21     ` Robert Klein
2022-09-26 16:13   ` Max Nikulin
2022-09-26 20:13     ` Tim Cross
2022-09-27 10:48       ` Should page break (^L) work as paragraph element separator and be included into Org syntax? (was: [BUG] org-fill-paragraph doesn't handle ^L correctly) Max Nikulin
2022-09-28  1:00         ` 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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7v4iawb.fsf@mfa.pw \
    --to=m@mfa.pw \
    --cc=emacs-orgmode@gnu.org \


* 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


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).