public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Does $DATADIR work?
Date: Wed, 23 May 2018 11:54:04 -0700 (PDT)	[thread overview]
Message-ID: <0ae3aee0-12a7-49eb-af28-9db4a5b39a41@googlegroups.com> (raw)
In-Reply-To: <20171019003223.GC25478@protagoras>


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



On Wednesday, October 18, 2017 at 7:32:16 PM UTC-5, John MacFarlane wrote:
>
> > 
> >     $DATADIR appears in the manual just as a placeholder for 
> >     whatever your user data directory is (see --data-dir). 
> >     The environment variable has no effect.  I've made a tweak 
> >     in the manual to make that clearer. 
> >     Note that the default user data dir is ~/.pandoc (on *nix), 
> >     so if you just symlink that wherever you like, that's the 
> >     most convenient solution. 
> > 
>

Would it be possible to implement that feature, i.e. define a custom 
$PDDATADIR environment variable to place the data anywhere in my $HOME 
directory? I'm in the weird situation of running pandoc on cygwin on 
windows, and it would be easier to add something to bashrc to tell pandoc 
where to look for templates and csl styles and forget omit the --data-dir 
option, unless I require it.

Cheers,

Luis.

-- 
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/0ae3aee0-12a7-49eb-af28-9db4a5b39a41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  reply	other threads:[~2018-05-23 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 13:34 BillS
     [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 [this message]
     [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=0ae3aee0-12a7-49eb-af28-9db4a5b39a41@googlegroups.com \
    --to=jlrn77-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).