public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Process multiple files with pandoc
Date: Thu, 31 Aug 2017 12:17:09 -0400	[thread overview]
Message-ID: <24c80671-c118-4d9f-58f8-96d70b273176@usa.net> (raw)
In-Reply-To: <57b91dde-4750-48a4-b79a-d8c9020b373e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

On 8/31/17 10:51 AM, Code Faster wrote:
> Hi!
> 
> I have a folder structure like
> 
> a.md
> c.md
> subfolder/b.md
> subfolder/subsubfolder/d.md
> 
> and I would like to transform them to e.g. latex like
> 
> a.md
> a.tex
> c.md
> c.tex
> subfolder/b.md
> subfolder/b.tex
> subfolder/subsubfolder/d.md
> subfolder/subsubfolder/d.tex
> 
> Do you know if there is a platform-independend command for this without 
> using bash or windows-shell?

Would Python or Perl count as platform-independent?  I don't think there 
is anything to do this in Pandoc itself, though it's fairly trivial in 
any shell or scripting language.

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.
---------------------------------------------------------------


  parent reply	other threads:[~2017-08-31 16:17 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 [this message]
2017-09-01  4:22   ` Kolen Cheung
2017-09-01  4:24   ` Kolen Cheung

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=24c80671-c118-4d9f-58f8-96d70b273176@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).