From: "'juh' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Do not build context file in /tmp
Date: Thu, 24 Jun 2021 18:59:29 +0200 [thread overview]
Message-ID: <20210624165929.GA10998@sokrates> (raw)
In-Reply-To: <CADAJKhChK6LhKSx3X-bi6G756V3XMOkyhi_gkv-ndMPQwSfTNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Hi BPJ,
Am Thu, Jun 24, 2021 at 04:07:29PM +0200 schrieb BPJ:
> I guess the proper workaround is to use a Makefile (or any build
> system/script of your choice) and have it build/assemble things with
> pandoc/context right in your project directory and then remove any junk
> automatically, rather than relying on pandoc running context. The learning
> curve of make is kind of steep, especially if you use it for things which
> differ from the most typical use cases but it pays off and gets less steep
> fairly quickly.
>
> https://www.google.com/search?q=alternatives+to+makefile
Thanks a lot for confirming. I'll go this way.
Ciao!
Jan Ulrich Hasecke
--
Autoren-Homepage: ......... http://literatur.hasecke.com
Satiren & Essays: ......... http://www.sudelbuch.de
Privater Blog: ............ http://www.hasecke.eu
Netzliteratur-Projekt: .... http://www.generationenprojekt.de
next prev parent reply other threads:[~2021-06-24 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 5:54 'juh' via pandoc-discuss
2021-06-24 14:07 ` BPJ
[not found] ` <CADAJKhChK6LhKSx3X-bi6G756V3XMOkyhi_gkv-ndMPQwSfTNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-24 16:59 ` 'juh' via pandoc-discuss [this message]
2021-06-28 17:26 ` 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=20210624165929.GA10998@sokrates \
--to=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).