From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: ivo welch <ivowel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: including '\usepackage{abc}` via command line option
Date: Sun, 19 May 2019 11:43:00 -0700 [thread overview]
Message-ID: <m2pnoeqo97.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <12e388cf-ccd2-4823-825e-a12cc4a57c58-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
ivo welch <ivowel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> thanks. works great now. much less painful.
>
> can I make a small suggestion? Use \IfFileExists{
> ~/.pandoc/templates/add2preamble.latex}{\input{
> ~/.pandoc/templates/add2preamble.latex}}{} or something like it to
> optionally include 'add2preamble.latex' (and equivalent 'add2preamble.ext'
> in other default files). This way, users can remain hedged against future
> changes to your default files if they just want to add some fragments.
We have --include-in-header, which adds things to the
latex preamble.
> PS: curious---what else is supposed to go into ~/.pandoc, so that these
> should go into ~/.pandoc/templates ?
See manual under --data-dir.
next prev parent reply other threads:[~2019-05-19 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 17:28 ivo welch
[not found] ` <674a937f-d17b-4c83-b293-e2163e089146-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-05-17 18:51 ` BPJ
[not found] ` <CADAJKhBoueM+P7N3-9Vq2aYKiu+Th3oVwpAwH2TMcaep65BEjw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-17 19:49 ` ivo welch
[not found] ` <d8907aaa-1e1f-4efd-9612-950b42917c33-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-05-17 20:13 ` John MacFarlane
[not found] ` <yh480ksgtcyh35.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-05-17 20:44 ` ivo welch
[not found] ` <ac6aece5-f574-4c66-946c-9f13f19c59cf-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-05-17 22:54 ` John MacFarlane
[not found] ` <yh480kk1eoy9mk.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-05-18 23:13 ` ivo welch
[not found] ` <12e388cf-ccd2-4823-825e-a12cc4a57c58-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-05-19 18:43 ` John MacFarlane [this message]
[not found] ` <m2pnoeqo97.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-05-19 20:13 ` ivo welch
2019-05-18 23:39 ` ivo welch
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=m2pnoeqo97.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=ivowel-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).