From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Greg S <elorian.mestec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Skipping commands in LaTeX document
Date: Thu, 09 Dec 2021 08:18:07 -0800 [thread overview]
Message-ID: <m28rwteoqo.fsf@Johns-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <4f3956c3-e028-473c-b622-dae2f0b72dedn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Greg S <elorian.mestec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Redefining \IPA and \makecell in latex fixes the problem as far as pandoc
> is concerned. But I am using these commands to generate the latex output
> that I want, so I don't want the redefinitions permanently within the latex
> source file. Is there a way to configure pandoc to only insert these when
> pandoc is processing the .tex file, so I have correct tables and no
> strikethrough when xelatex is processing the file?
You could automate this in a variety of ways. For example,
you could add \include{extras} in your latex file, and
then have extras_for_pandoc.tex containing the special definitions,
and extras_for_latex.tex not containing them (maybe empty).
Before running latex on the file, symlink extras.tex to
extras_for_latex.tex. Before running pandoc, symlink it
to extras_for_pandoc.tex. Put this all in a Makefile so
you don't have to think about it.
Or you could use a conditional in your latex file that is
sensitive to something you can set on the command line.
next prev parent reply other threads:[~2021-12-09 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 1:16 Greg S
[not found] ` <0462fc42-ae24-4c52-b267-1126ed5834edn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-04 17:36 ` John MacFarlane
[not found] ` <m2zgpgi869.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-12-05 2:50 ` Greg S
[not found] ` <bac7947b-259e-4774-b993-33f69fffc05fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-05 18:56 ` John MacFarlane
[not found] ` <m2r1aqhod6.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-12-05 19:53 ` Greg S
[not found] ` <84e207d9-eaed-4b24-8b6b-62ea07bb2b5bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-05 20:11 ` John MacFarlane
[not found] ` <m2fsr6hkvl.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-12-06 4:25 ` Greg S
[not found] ` <c648fb98-d892-4f1e-b3aa-0da071d8de4bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-06 10:34 ` BPJ
[not found] ` <CADAJKhCC9xm6HX0aF5SzJr9vG3xZR1eiQxxCpA6QNRi1BRE-7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-12-09 3:03 ` Greg S
[not found] ` <4f3956c3-e028-473c-b622-dae2f0b72dedn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-09 16:18 ` John MacFarlane [this message]
2021-12-06 17:57 ` John MacFarlane
-- strict thread matches above, loose matches on Subject: below --
2021-12-04 0:34 'Greg Shuflin' via pandoc-discuss
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=m28rwteoqo.fsf@Johns-Air.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=elorian.mestec-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).