From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: how to force pagebreaks
Date: Fri, 13 Sep 2019 15:14:28 -0400 [thread overview]
Message-ID: <5c11e555-df2d-2a01-af29-9bdb7bf67c84@usa.net> (raw)
In-Reply-To: <4fadd2ef-820b-4dc9-b7b7-97aab7232543@default>
On 9/13/19 3:04 PM, Don Raikes wrote:
> Hello,
>
> I am just getting started on my first pandoc project. I am breaking my
> project into multiple markdown files each of which starts with a level-2
> header “##”.
>
> How do I tell pandoc to force page breaks at each level-2 header?
>
What's your output format? Markdown has no idea of 'pages', so a page
break in markdown doesn't really mean anything.
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5c11e555-df2d-2a01-af29-9bdb7bf67c84%40usa.net.
next prev parent reply other threads:[~2019-09-13 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 19:04 Don Raikes
2019-09-13 19:14 ` Daniel Staal [this message]
[not found] ` <5c11e555-df2d-2a01-af29-9bdb7bf67c84-Jdbf3xiKgS8@public.gmane.org>
2019-09-17 13:47 ` Ghislain Vaillant
[not found] ` <26ece219-65a0-46ba-b10b-d3d8a7350c07-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-25 8:01 ` Agustín Martín
2019-09-13 19:29 ` BP Jonsson
2020-02-05 14:18 ` Ignacio Jonatan Hernández López
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=5c11e555-df2d-2a01-af29-9bdb7bf67c84@usa.net \
--to=dstaal-jdbf3xikgs8@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).