public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Bernardo C. D. A. Vasconcelos" <bernardovasconcelos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Issue chaining Lua Filters
Date: Wed, 15 Mar 2023 15:49:46 -0700 (PDT)	[thread overview]
Message-ID: <022d6e2f-c5f7-4786-a811-ad089ceb8864n@googlegroups.com> (raw)
In-Reply-To: <05538ba3-fd8c-41ca-b0c4-09fa9d9ba71en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1708 bytes --]

It turns out I had to add `doc.meta.references = pandoc.utils.references(doc
)` to the multibib filter and that's it. 
Issue closed.

On Wednesday, March 15, 2023 at 4:58:50 PM UTC-3 Bernardo C. D. A. 
Vasconcelos wrote:

> Hello everyone,
>
> I posted this issue <https://github.com/pandoc-ext/multibib/issues/4> to 
> Github and wanted to ask you for input. In short, the problem is that the 
> citefield 
> <https://github.com/bcdavasconcelos/citefield/blob/main/_extensions/citefield/citefield.lua> 
> filter works when run after citeproc 
> <https://github.com/bcdavasconcelos/citefield/blob/main/_extensions/citefield/citeproc.lua>, 
> but not when run after multibib 
> <https://github.com/pandoc-ext/multibib/blob/main/_extensions/multibib/multibib.lua>. 
> These are different filters, so there is no surprise there. I am trying to 
> understand how the citeproc and the multibib filters differ in terms of 
> what they pass on to the filters that come next in the chain. Is it 
> possible that the multibib is altering the AST content in some 
> irrecoverable way and can't work together with the citefield filter? Or 
> should this just be a matter of retrieving the information in the correct 
> way?
>
> Thanks for any comments and insights,
> B.
>

-- 
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/022d6e2f-c5f7-4786-a811-ad089ceb8864n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 6915 bytes --]

      parent reply	other threads:[~2023-03-15 22:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 19:58 Bernardo C. D. A. Vasconcelos
     [not found] ` <05538ba3-fd8c-41ca-b0c4-09fa9d9ba71en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-15 22:49   ` Bernardo C. D. A. Vasconcelos [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=022d6e2f-c5f7-4786-a811-ad089ceb8864n@googlegroups.com \
    --to=bernardovasconcelos-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).