From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "Clément Aubert"
<aubert.clement-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Structure of the outputfile variable in template
Date: Sat, 15 May 2021 16:54:17 -0700 [thread overview]
Message-ID: <m2h7j3mu3a.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <e266f9ed-a1df-4469-a773-127cdf488845n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
At this time, no, it's just a string.
Clément Aubert <aubert.clement-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hi,
>
> If I'm not mistaken, since
> https://github.com/jgm/pandoc/commit/699d289cc5913c3cb0ec7b1b3d7ae767cbe55339
> we can access the `sourcefile` and `outputfile`variables from the templates.
>
> Do those variables have any structure?
> Currently the `inputfile` and `outputfile` would contain e.g.
> `docs/about.md`
> and
> `docs/about.html`,
>
> Is there an way to extract the file name (about), the path (docs/), the
> extension (.md or .html), or a combination of those?
>
> I feel that this variables are not arrays and could not find my answer in
> https://pandoc.org/MANUAL.html#templates
>
> Thanks!
> Clément.
>
> --
> 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/e266f9ed-a1df-4469-a773-127cdf488845n%40googlegroups.com.
--
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/m2h7j3mu3a.fsf%40MacBook-Pro.hsd1.ca.comcast.net.
next prev parent reply other threads:[~2021-05-15 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 19:09 Clément Aubert
[not found] ` <e266f9ed-a1df-4469-a773-127cdf488845n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-15 23:54 ` John MacFarlane [this message]
[not found] ` <m2h7j3mu3a.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-17 0:00 ` Clément Aubert
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=m2h7j3mu3a.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=aubert.clement-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).