From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Process multiple files with pandoc
Date: Thu, 31 Aug 2017 21:24:44 -0700 (PDT) [thread overview]
Message-ID: <bad07d20-0335-400f-b6c8-683c3f6ef8b3@googlegroups.com> (raw)
In-Reply-To: <57b91dde-4750-48a4-b79a-d8c9020b373e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
Or, on other words, may be you can be more specific on the requirements, like what do you want to achieve. (I guess to some extend makefile can be used on Windows too? And then there is Cmake.)
prev parent reply other threads:[~2017-09-01 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 14:51 Code Faster
[not found] ` <57b91dde-4750-48a4-b79a-d8c9020b373e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-31 16:17 ` Daniel Staal
2017-09-01 4:22 ` Kolen Cheung
2017-09-01 4:24 ` Kolen Cheung [this message]
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=bad07d20-0335-400f-b6c8-683c3f6ef8b3@googlegroups.com \
--to=christian.kolen-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).