From: BillS <shaverb-LTqONF+Zze4dnm+yROfE0A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Does $DATADIR work?
Date: Wed, 18 Oct 2017 06:34:54 -0700 (PDT) [thread overview]
Message-ID: <fe0be057-6f62-462c-a784-5d1ce4963ccc@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1338 bytes --]
I have been asked to set up pandoc for an HPC cluster and while most of the
set up has gone fairly smoothly, we are having issues resolving the path to
the templates and other "data" files -- they resolve to the build directory
not the install directory.
When we test with the --data-dir argument it works fine, but we would like
to be able to set it 'once and forever'. In the man pages/user guide it
looks as though there is an option to set an environment variable
($DATADIR) that would do the same thing as the command line argument, but
we have not been able to get that to work.
Is the $DATADIR environment variable supported? Is there a better way to
'once and forever' point to the correct data directory?
Thank you for any hints and pointers.
--
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/fe0be057-6f62-462c-a784-5d1ce4963ccc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1843 bytes --]
next reply other threads:[~2017-10-18 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 13:34 BillS [this message]
[not found] ` <fe0be057-6f62-462c-a784-5d1ce4963ccc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-18 15:52 ` John MacFarlane
[not found] ` <20171018155238.GF78597-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-18 18:28 ` BillS
[not found] ` <07f482a3-86ca-4b30-9dfe-d15c6c6ce68b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-19 0:32 ` John MACFARLANE
2018-05-23 18:54 ` Luis Rivera
[not found] ` <0ae3aee0-12a7-49eb-af28-9db4a5b39a41-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-05-24 3:58 ` Kolen Cheung
2017-10-19 10:30 ` 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=fe0be057-6f62-462c-a784-5d1ce4963ccc@googlegroups.com \
--to=shaverb-ltqonf+zze4dnm+yrofe0a@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).