public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: lf-araujo <luis.nando-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Here is a building system for complex pandoc documents, testing needed
Date: Thu, 11 May 2017 00:59:44 -0700 (PDT)	[thread overview]
Message-ID: <83a45d4b-4b18-4cbf-868a-45324849a3a7@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1139 bytes --]



Hi everyone,

I have been working in a small utility that standardizes the folder 
structure for the production of complex pandoc documents. I have tested it 
in about 20 projects of mine and only now feel more comfortable sharing. 
Could you please explore and test? I am open for suggestions.

You can go get you hands dirty right away with:


wget http://tiny.cc/mighty_make -O Makefile

And run make help, or read about the project here 
<https://lf-araujo.github.io/lf-araujo.github.io/2017/04/08/mightymake.html>
.

Best,

lf
​

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/83a45d4b-4b18-4cbf-868a-45324849a3a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 3764 bytes --]

             reply	other threads:[~2017-05-11  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  7:59 lf-araujo [this message]
     [not found] ` <83a45d4b-4b18-4cbf-868a-45324849a3a7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-05-11  8:42   ` John MacFarlane
2017-08-28  2:20   ` lf-araujo

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=83a45d4b-4b18-4cbf-868a-45324849a3a7@googlegroups.com \
    --to=luis.nando-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).