Re: 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 <manikulin@gmail.com>]

On 27/09/2022 03:13, Tim Cross wrote:
> Max Nikulin writes:
>> On 26/09/2022 18:39, Ihor Radchenko wrote:
>>> Should we add page break (^L) to our syntax? It sounds like a reasonable
>>> addition for a text-based markup.
>>
>> I do not have strong opinion. It is a control character while I prefer explicit markup and
>> printable characters or commands in such case. On the other hand the character is widely
>> used in .el files.
>>
>> Users may expect \newline when ^L is exported to LaTeX.
> 
> I think I'm with you as well. I don't have a strong opinion and while
> personally, I don't like control characters used as part of the syntax,
> ^L is often used in elisp files, so ......

Matt, could you, please, provide some details concerning your use case 
for ^L in Org files? Even if nothing will change this time, it may 
affect later decisions.

On 27/09/2022 13:21, Robert Klein wrote:
 > On Tue, 27 Sep 2022 01:10:49 +1000
 > Matt Beshara wrote:

 >> Fair enough.  If the consensus from others is that ^L should be
 >> recognised as a paragraph separator and the code is eventually
 >> written to make that work, that would be nice, but as it stands I
 >> can just start adding newlines after ^L.
 >
 > Actually ^L is a *page* separator (to be exact “FORM FEED”).

I have realized that page separator for plain text is not necessary 
paragraph separator. The same paragraph may continue on the next page. 
It makes things more tricky. ^L should be kept on its own line while 
text around should be wrapped.

However from a discussion happened a year ago I concluded that it may be 
not so trivial to tune `org-fill-element' for special cases.

Timothy. Re: [PATCH] Don't fill displayed equations. Sun, 03 Oct 2021 
16:50:54 +0800. https://list.orgmode.org/875yueij6r.fsf@gmail.com