From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'Karl Weber' via pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to specify number-offset?
Date: Sun, 27 Sep 2020 16:02:23 -0700 [thread overview]
Message-ID: <m2v9fy258g.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <200b15bc-f323-487e-b39d-e6be8845eacan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
No, you can't specify it in YAML metadata.
"'Karl Weber' via pandoc-discuss"
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:
> Hi,
>
> I do want to specify number-offset neither on the commandline of pandoc nor
> in the defaults yaml file. The reason is, that I have a project consisting
> of a number of documents in markdown format, that I want to convert to
> html5 using make. Hence I need to specify number-offset for each file
> individually.
>
> Is there some way to do this?
>
> I tried to specify it in a yaml block at the beginning of each file,
> something like the following:
>
> ---
> output:
> html_document:
> pandoc_args: [
> "--number-offset=4,0"
> ]
> ---
>
> I tried different variations of this example, but none worked. Note, that
> my input format ist pandoc markdown.
>
> It would be great, if something like that would work. I would appreciate
> any help.
>
> Thanks in advance,
> Karl
>
>
> --
> 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/200b15bc-f323-487e-b39d-e6be8845eacan%40googlegroups.com.
next prev parent reply other threads:[~2020-09-27 23:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 17:07 'Karl Weber' via pandoc-discuss
[not found] ` <200b15bc-f323-487e-b39d-e6be8845eacan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-27 23:02 ` John MacFarlane [this message]
[not found] ` <m2v9fy258g.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-28 6:08 ` 'Karl Weber' via pandoc-discuss
[not found] ` <1c0310ae-6348-4ba6-8d9d-746aab5e0c09n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-28 18:32 ` 'Karl Weber' via pandoc-discuss
[not found] ` <90ec5cf3-3f74-4ae2-94a9-66d60d007ee1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-29 6:09 ` 'Karl Weber' via pandoc-discuss
2020-09-28 19:02 ` John MacFarlane
[not found] ` <m2pn65208q.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-28 19:10 ` 'Karl Weber' via pandoc-discuss
[not found] ` <c8b8ecf4-1f85-497d-ad85-aedeb96a4f2an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-28 21:53 ` John MacFarlane
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=m2v9fy258g.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).