emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Beshara <m@mfa.pw>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: 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 [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt/Code/emacs/lisp/org/)])
Date: Tue, 27 Sep 2022 01:10:49 +1000	[thread overview]
Message-ID: <87y1u6415o.fsf@mfa.pw> (raw)
In-Reply-To: <87mtamjrft.fsf@localhost>

> ^L is not a part of Org specification for paragraph separators.
> According to 
> https://orgmode.org/worg/dev/org-syntax.html#Paragraphs,
> paragraph boundaries should either be empty lines, or beginning 
> of other
> Org elements.

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.

Thanks for your work on Org mode!
Matt


  reply	other threads:[~2022-09-26 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 23:39 [BUG] org-fill-paragraph doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt/Code/emacs/lisp/org/)] Matt Beshara
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 [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87y1u6415o.fsf@mfa.pw \
    --to=m@mfa.pw \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.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/org-mode.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).