From: "Matthias Güdemann" <matthias.gudemann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Issue with single Latex run producing incomplete pdf
Date: Mon, 27 Nov 2023 09:06:26 -0800 (PST) [thread overview]
Message-ID: <c17d418c-d9c5-469a-bf07-089ef375fb9bn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1181 bytes --]
Hi all,
since the following commit
```
bb36f127e * LaTeX template: include bookmark package unconditionally.`
```
I get an incomplete pdf output for slides based on beamer. The first slide
is incomplete, slide numbers are incorrect and headers are missing.
Creating a .tex and running xelatex / lualatex two times produces the
desired output, running either only once reproduces the effect of the
incomplete pdf.
The commit message of the above commit states
```
As a consequence, we now default to running LaTeX only
once in producing a PDF (instead of twice). If a table
of contents is present, we still have to run three times
to get the page numbers.
```
is there a way to force running latex twice/thrice even if there is not toc?
best regards
Matthias
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c17d418c-d9c5-469a-bf07-089ef375fb9bn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1775 bytes --]
next reply other threads:[~2023-11-27 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 17:06 Matthias Güdemann [this message]
[not found] ` <c17d418c-d9c5-469a-bf07-089ef375fb9bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-27 19:00 ` John MacFarlane
[not found] ` <48242F5E-8DF4-49AD-BC67-6B74A5EA0111-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-11-27 19:35 ` BPJ
[not found] ` <CADAJKhCsDHPO-L_U5vix4pasj9AswJgX6A83pJw+0-caEbmVaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-28 4:45 ` John MacFarlane
2023-11-28 9:35 ` Matthias Güdemann
[not found] ` <CAGkX0vcD1C4k38YTnW2sY0fidLdBgOvdOXtpBxT1x22_m20Lbg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-28 16:58 ` John MacFarlane
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=c17d418c-d9c5-469a-bf07-089ef375fb9bn@googlegroups.com \
--to=matthias.gudemann-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).