From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Norman Ramsey
<fellswalker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to add a `\usepackage` in a Lua filter meant to support LaTeX?
Date: Fri, 20 Nov 2020 11:43:44 -0800 [thread overview]
Message-ID: <m21rgnhkzz.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <2e27c210-a276-4319-abd7-c81d5db7f7d7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Norman Ramsey <fellswalker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> I've got a Lua filter that is meant to render certain document elements in
> a `boxedminipage` environment. To accomplish this feat, I give the element
> in a suitable `div`, and a Lua filter inserts the LaTeX environment. The
> document itself remains universal, but the Lua filter is resolutely
> intended for LaTeX.
>
> The filter adds a raw `\usepackage{boxedminipage2e}` to the
> `header-includes` of the metadata, but unfortunately when `-V
> header-includes=...` appears on the command line, it takes precedence and
> the document metadata is ignored.
>
> I thought of trying to use `-M header-includes=...` instead of `-V
> header-includes=...`, but that comes with its own problems: using the `-M`
> option, the argument on the command line is escaped. It is not clear to me
> if there is a mechanism I can use to put raw LaTeX in that spot.
Why couldn't the filter add to the metadata `header-includes`
RawBlock (Format "latex") "\\usepackage{boxedminipage2e}"
?
Wouldn't that be a solution?
next prev parent reply other threads:[~2020-11-20 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHWvqoEJV35v23+VkitO4uJW9kmTKnP3L8H>
2020-11-19 19:27 ` Norman Ramsey
[not found] ` <2e27c210-a276-4319-abd7-c81d5db7f7d7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-19 19:50 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
[not found] ` <e6b951c36db0463983df5a4c381693ea-FfwAq0itz3ofv37vnLkPlQ@public.gmane.org>
2020-11-19 21:08 ` Norman Ramsey
[not found] ` <6f859587-fd58-46b5-b94b-a21bebe3e6fcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-20 10:22 ` krulis....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2020-11-19 20:10 ` John MacFarlane
2020-11-20 15:54 ` BPJ
2020-11-20 19:43 ` John MacFarlane [this message]
[not found] ` <m21rgnhkzz.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-20 21:04 ` Norman Ramsey
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=m21rgnhkzz.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=fellswalker-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).