From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Explicit page breaks
Date: Thu, 29 Sep 2022 13:05:40 +0700 [thread overview]
Message-ID: <th3cjl$13ul$1@ciao.gmane.io> (raw)
In-Reply-To: <87sfkaague.fsf@posteo.net>
Let me remind that the discussion originates from a complain that
filling paragraph does not respect ^L character in the .org file. The
topic starter have not provided more details concerning their use case,
maybe it is irrelevant to export.
During export (LaTeX is not the only case, even HTML may be printed or
saved as PDF and has some CSS attributes) \clearpage (or its equivalent)
may be attributed to the end of a block level element or a beginning of
it. In the latter case it should be preserved even if the previous
heading is commented out. It resembles to a recent topic discussing
wrapping exported heading or other elements into some template.
I agree that page breaking inside paragraph (at particular point or when
current line is filled) is a different case. Degree of support may vary
across export backends.
next prev parent reply other threads:[~2022-09-29 6:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 9:09 Create in Org a bilingual book with facing pages Juan Manuel Macías
2022-09-27 12:29 ` Ihor Radchenko
2022-09-27 16:50 ` Juan Manuel Macías
2022-09-28 3:15 ` Ihor Radchenko
2022-09-28 7:50 ` Explicit page breaks (was: Create in Org a bilingual book with facing pages) Juan Manuel Macías
2022-09-29 3:13 ` Ihor Radchenko
2022-09-29 5:29 ` Explicit page breaks Juan Manuel Macías
2022-09-29 6:05 ` Max Nikulin [this message]
2022-09-29 6:21 ` Thomas S. Dye
2022-10-03 7:14 ` Ihor Radchenko
2022-10-04 20:24 ` Juan Manuel Macías
2022-10-05 7:59 ` Ihor Radchenko
2022-09-27 16:34 ` Create in Org a bilingual book with facing pages Hendursaga
2022-09-28 6:14 ` Juan Manuel Macías
2022-09-28 14:14 ` Hendursaga
2022-09-28 15:14 ` Juan Manuel Macías
2022-09-28 7:14 ` Christian Moe
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='th3cjl$13ul$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).