public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'juh' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	Pandoc Mailinglist
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Do not build context file in /tmp
Date: Mon, 28 Jun 2021 10:26:22 -0700	[thread overview]
Message-ID: <m2bl7pnbnl.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20210624055435.GA11054@sokrates>


You could try

TMPDIR=. pandoc in.md -o out.pdf -t context

but this might have other bad effects!

"'juh' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
writes:

> Hi all,
>
> am I right that pandoc uses /tmp to build the intermediate context
> source file?
>
> My problem is that I have a hierarchy of supporting files relative to
> the directory of the markdown source file which context needs to build
> correctly.
>
> While:
>
> pandoc -t context -o test.tex test.md
> context test.tex
>
> works fine
>
> pandoc -t context --pdf-engine=context -o test.pdf test.md
>
> throws error as multiple context environments are not found.
>
> There is a work around by putting all supporting files in a special
> folder of the context distribution 
>
> context/tex/texmf-local
>
> You have to call "context --generate" the make any changes in this path
> known to context. This is annoying but possible.
>
> But the path to the original source folder is lost so that it is
> impossible to include things stored along with the source file.
>
> projectdir/source.md
> projectdir/image.png
>
> When context is called inside the project folder it is of course
> possible to include the image file.  When context is called on a tmp
> file in /tmp the path is lost.
>
> Is there a switch to build all files in the working directory?
>
> 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
>
>
> -- 
> 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/20210624055435.GA11054%40sokrates.


      parent reply	other threads:[~2021-06-28 17:26 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
2021-06-28 17:26 ` John MacFarlane [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=m2bl7pnbnl.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).