From: Ihor Radchenko <yantar92@posteo.net>
To: "Marvin Gülker" <post+orgmodeml@guelker.eu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: export form feed as page break
Date: Sun, 22 Oct 2023 08:58:08 +0000 [thread overview]
Message-ID: <87bkcrava7.fsf@localhost> (raw)
In-Reply-To: <87fs24x6w3.fsf@guelker.eu>
Marvin Gülker <post+orgmodeml@guelker.eu> writes:
> ...
> On the other hand, there are semantic page breaks. The page break I
> described in the OP is of this kind – it has been added specifically to
> hide the proposed solution from the first page and allow me to just
> print page 1 and hand that one to the students. For this page break, the
> paper size is completely irrelevant. Even if I printed on A3 for
> whatever reason (maybe I ran out of A4 paper), the semantic still
> requires the solution to be on page 2. It is this kind of page break I
> am referring to and which I think is representable in markup.
Fair point. And adding "semantic" page breaks to Org syntax will not
rule out "typographical" page breaks via @@backend:...@@ or macro syntax.
>> - In LaTeX, this is easy to achieve simply putting =\clearpage=
>
> A quick note here: \newpage and \clearpage do different things in LaTeX
> if there is floating material in the document. \clearpage typesets the
> floats and then breaks the page, whereas \newpage does not consider them.
If we consider semantic page breaks, I think that \newpage is more
appropriate as it will prevent floats defined below from showing up.
--
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:[~2023-10-22 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 7:42 Feature request: export form feed as page break Marvin Gülker
2023-10-21 9:19 ` Ihor Radchenko
2023-10-21 14:43 ` Max Nikulin
2023-10-22 8:54 ` Ihor Radchenko
2023-10-21 16:33 ` Marvin Gülker
2023-10-22 8:58 ` Ihor Radchenko [this message]
2023-10-21 14:26 ` Max Nikulin
2023-10-21 16:27 ` Marvin Gülker
2023-10-22 9:00 ` Ihor Radchenko
2023-10-23 10:37 ` Max Nikulin
2023-10-22 6:00 ` Jambunathan K
2023-10-22 12:55 ` Uwe Brauer
2023-10-24 6:08 ` Marvin Gülker
2024-01-07 7:23 ` Timothy
2024-01-07 12:57 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkcrava7.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=post+orgmodeml@guelker.eu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.