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 use Lua filter to insert elements before title?
Date: Mon, 31 Aug 2020 11:43:02 -0700 [thread overview]
Message-ID: <m2d036y7ux.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <f6a8164f-db8a-4c16-83a1-199dce28ab8en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Sure. You can modify metadata using a lua filter.
So, just change the `include-before` metadata field
to include your navigation.
Norman Ramsey <fellswalker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> I'm using a Lua filter to construct a navigation bar, which I'd like to
> have appear as the very first thing on a standalone HTML page. However,
> looking at `pandoc -D html`, it appears that the metadata title is inserted
> before anything in the body that I build using the Lua filter. So my
> navigation bar doesn't show up until after the page title, which is not the
> result I was hoping for.
>
> Is there a way for me to alter the `include-before` list from within a Lua
> filter? Or is there some other approach I should be taking to this problem?
>
>
> Norman Ramsey
>
> --
> 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/f6a8164f-db8a-4c16-83a1-199dce28ab8en%40googlegroups.com.
prev parent reply other threads:[~2020-08-31 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 18:18 Norman Ramsey
[not found] ` <f6a8164f-db8a-4c16-83a1-199dce28ab8en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-31 18:43 ` 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=m2d036y7ux.fsf@johnmacfarlane.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).