From: RHvdG <rhvandergaag-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How do I tell pandoc to use only H1 headings for headers?
Date: Sun, 19 Jun 2022 07:52:13 -0700 (PDT) [thread overview]
Message-ID: <e61310f0-b3c6-4a6f-87e8-28f8e5428018n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]
Newbie here; patience is a virtue. I am writing a book in markdown using
Vim, and making use of André Miede's 'ClassicThesis' style through this
<https://github.com/norangebit/LaTeKiSS> pandoc template. It all works very
well, but my H2 headers are too long to appear (also) as page headers in
the output PDF, so I would like to tell pandoc to use the H1 headers (one
for each part of the book) for that. And I can't seem to figure out how.
Help is much appreciated.
--
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/e61310f0-b3c6-4a6f-87e8-28f8e5428018n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1181 bytes --]
next reply other threads:[~2022-06-19 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 14:52 RHvdG [this message]
[not found] ` <e61310f0-b3c6-4a6f-87e8-28f8e5428018n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-21 9:45 ` Bastien DUMONT
2022-06-21 12:07 ` RHvdG
[not found] ` <13c06d73-0001-4ad1-b414-4038b1aa7caan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-21 12:32 ` AW: " denis.maier-NSENcxR/0n0
2022-06-21 13:21 ` Bastien DUMONT
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=e61310f0-b3c6-4a6f-87e8-28f8e5428018n@googlegroups.com \
--to=rhvandergaag-re5jqeeqqe8avxtiumwx3w@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).