From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Latex command in header inclusion munged with \textbackslash{}
Date: Mon, 7 Aug 2017 11:25:46 -0700 [thread overview]
Message-ID: <20170807182546.GB91733@airbears2-10-142-0-86.airbears2.1918.berkeley.edu> (raw)
In-Reply-To: <85d3801f-6a20-4873-bf2e-e8cd7f13445e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
See https://github.com/jgm/pandoc/issues/2956
Alternatively, in the dev version of pandoc you can tell
it you've got raw latex, not Markdown:
header-includes:
- `\let\oldsection\section`{=latex}
Final remark: I don't understand why it's not parsing
the `\section` as raw tex. I'll need to look into this;
it may be a bug in the LaTeX reader.
+++ David Nebauer [Aug 07 17 00:39 ]:
> If I process this markdown file ('mwe-latex.md'):
> ---
> title: "Minimal Working Example"
> header-includes:
> - \let\oldsection\section
> - \renewcommand{\section}[1]{\clearpage\oldsection{#1}}
> ---
> Text.
> with the pandoc command:
> pandoc -t latex --latex-engine=xelatex --output=mwe-latex.pdf
> mwe-latex.md
> I get the the error:
> ! LaTeX Error: Missing \begin{document}.
> See the LaTeX manual or LaTeX Companion for explanation.
> Type H <return> for immediate help.
> ...
> l.49 \let\oldsection\textbackslash{}s
> pandoc: Error producing PDF
> On generating latex output with the command:
> pandoc -t latex --latex-engine=xelatex --standalone
> --output=mwe-latex.tex mwe-latex.md
> and examining line 49 of the output file it becomes apparent that this
> line from the header inclusion:
> \let\oldsection\section
> has been munged by pandoc to:
> \let\oldsection\textbackslash{}section
> and this is causing the processing problem. (Note: changing latex
> engines makes no difference.)
> Once line 49 is edited to resemble the original command from the header
> inclusion the error disappears.
> How can I prevent this latex command in the header inclusion from being
> munged by pandoc?
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/85d3801f-6a20-4873-
> bf2e-e8cd7f13445e%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/85d3801f-6a20-4873-bf2e-e8cd7f13445e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-08-07 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 7:39 David Nebauer
[not found] ` <85d3801f-6a20-4873-bf2e-e8cd7f13445e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-07 18:25 ` John MacFarlane [this message]
[not found] ` <20170807182546.GB91733-qqGlgsTyhTiCiGiXOSDXzGEIDr1rnHf9vtmmnBSr4lwnUAKC5xwfQhvRwXAb8BAkh13vi7wywA4@public.gmane.org>
2017-08-08 13:56 ` David Nebauer
[not found] ` <1cef78af-0bfb-4d45-983b-39863c588bb6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-09 17:54 ` Roland Hieber
[not found] ` <6dc05b9e-b1fd-cf4c-6d6b-8b6adb9a1df0-NSJBNaQhiPN7tPAFqOLdPg@public.gmane.org>
2017-08-10 11:10 ` David Nebauer
2017-08-08 14:02 ` David Nebauer
[not found] ` <c39d6355-1b71-4355-813f-5e85a1beb988-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-09 19:33 ` BP Jonsson
[not found] ` <eca11bcc-3eeb-a426-dcb6-7a70d4b411e4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-09 19:36 ` BP Jonsson
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=20170807182546.GB91733@airbears2-10-142-0-86.airbears2.1918.berkeley.edu \
--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).