From: jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: trouble with hyperref loaded after `header-includes` in the default latex template
Date: Mon, 10 Apr 2023 16:12:19 +0800 (GMT+08:00) [thread overview]
Message-ID: <u10gdp$qsi$1@ciao.gmane.io> (raw)
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
I get an error
`cleverref must be loaded after hyperref`,
after updating.
I find in the default latex template that hyperref package is deferred to be loaded after `header-includes`, while I usually put 3rd packages including cleverref in it.
I know I can use customized template. But I'd like to figure out where should I put those packages that are required to be load after hyperref with the default template.
--
next reply other threads:[~2023-04-10 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 8:12 jiewuza [this message]
2023-04-10 10:56 ` Ulrike Fischer
2023-04-10 13:40 ` jiewuza
2023-04-10 14:13 ` Ulrike Fischer
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='u10gdp$qsi$1@ciao.gmane.io' \
--to=jiewuza-9onoh4p/ygk@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).