From: Daurnimator <quae-l4MFkWPWeOkX2WXlbB3fKg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Error parsing tex with %\ after empty line inside of block
Date: Mon, 9 Mar 2015 15:41:51 -0400 [thread overview]
Message-ID: <CAEnbY+eFE7D-G9aKST2MO-xdrNCqURnYZOrG=Ost2gs_jduzyQ@mail.gmail.com> (raw)
In-Reply-To: <20150309193104.GB8520-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
On 9 March 2015 at 15:31, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
> It actually has nothing to do with the %. The problem is the blank line
> inside \title{...}.
>
> This sufficies to reproduce the problem:
>
> ```
> \title{
> Test
>
> }
> ```
>
> But note! This won't compile with pdflatex either. You can't have a blank
> line inside \title{}.
> I don't think it's a bug if pandoc chokes on invalid latex.
xelatex seems to allow it.
I get the same error passing --latex-engine=xelatex
Some background: I wanted to see how pandoc compiled
https://github.com/wahern/cqueues/blob/master/doc/cqueues.tex
next prev parent reply other threads:[~2015-03-09 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 16:20 Daurnimator
[not found] ` <CAEnbY+dCD2Hp9_Py+9o5zP88JjyuCBMWbqM3bg5hDX=FDXXbxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-09 19:31 ` John MacFarlane
[not found] ` <20150309193104.GB8520-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-03-09 19:41 ` Daurnimator [this message]
[not found] ` <CAEnbY+eFE7D-G9aKST2MO-xdrNCqURnYZOrG=Ost2gs_jduzyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-10 0:27 ` John MacFarlane
[not found] ` <20150310002710.GA12098-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-03-10 16:43 ` John MacFarlane
[not found] ` <20150310164339.GH67493-0VdLhd/A9Pm0ooXD8Eul3QV/cM5bZUxVaxvHy9gZ5WyVc3sceRu5cw@public.gmane.org>
2015-03-10 17:01 ` Daurnimator
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='CAEnbY+eFE7D-G9aKST2MO-xdrNCqURnYZOrG=Ost2gs_jduzyQ@mail.gmail.com' \
--to=quae-l4mfkwpweokx2wxlbb3fkg@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).