public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: John Bentley
	<johnny.bentley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Is $header-includes$ too high in default.latex?
Date: Sat, 08 May 2021 08:36:58 -0600	[thread overview]
Message-ID: <m2im3t8f79.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <0c7b7414-fe12-41c3-8978-731808fe79b5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


We've put it as late as possible in the template.
The reason it's not at the very end is that some things
really need to be loaded as late as possible -- if you
look at the changes in this template over time, you'll
see that the migration of header-incldes up was driven
by some real problems.

But it might not be optimal; it could be that we've added
some things to the end of the preamble that don't need to
be there.

I know there's a good reason the language-related and
bibi stuff comes before header-includes.  But the csl commands,
natbib/bibtex commands, and csquotes commands maybe could
move up.  We'd need to check the logs to mae sure there's
not a good reason they're there.  go ahead and submit an
issue on the GitHub tracker so we can think more about this.

John Bentley <johnny.bentley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> The option `--include-in-header` is specified to "Include contents of FILE, 
> verbatim, at the end of the header". 
> https://pandoc.org/MANUAL.html#option--include-in-header
>
> The option `--include-in-header` sets the template variable `$
> header-includes$`.
>
> However, in default.latex the `$header-includes` variable is placed quite 
> high in the header, preceding quite a number of latex header commands. 
> Shouldn't  `$header-includes` be placed just before `\begin{document}`?
>
> My motivation is to override prior default settings. Specifically I'm 
> trying to override `\setlength{\csllabelwidth}{3em}` that gets spit out in 
> the header when processing citations.
>
> I *can* do this by using --include-before-body/$include-before$ instead. 
> But that seems like abusing what should be a content option rather than a 
> coding option.
>
> Of course I could alter default.latex at my end, and use a custom default 
> template. But I'm trying to avoid that path.
>
> So, is $header-includes$ too high in default.latex?
>
> -- 
> 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/0c7b7414-fe12-41c3-8978-731808fe79b5n%40googlegroups.com.


      parent reply	other threads:[~2021-05-08 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 22:31 John Bentley
     [not found] ` <0c7b7414-fe12-41c3-8978-731808fe79b5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-08 14:36   ` John MacFarlane [this message]

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=m2im3t8f79.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=johnny.bentley-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).