From: kiko.fernandez-1zs4UD6AkMk@public.gmane.org
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Creation of a filter that accepts an option
Date: Fri, 5 Oct 2018 03:33:09 -0700 (PDT) [thread overview]
Message-ID: <f91cf9f6-8d38-43ac-b3a5-b21070c66e14@googlegroups.com> (raw)
In-Reply-To: <m2d0spu1eu.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1480 bytes --]
Hi John,
thanks for your advise. However, wouldn't this apply the my filter, named
filters, first and then the pandoc-cross-ref?
FILTERING_MODE=WITH_COMMENTS pandoc -s -f markdown -F filters -F
pandoc-crossref meta.yaml -o test.pdf TEST.md
In any case, I tried changing the order and didn't get it to work without
pattern matching on the Str data value.
I found that weird.
On Thursday, October 4, 2018 at 6:23:05 PM UTC+2, John MacFarlane wrote:
>
> kiko.fe...-1zs4UD6AkMk@public.gmane.org <javascript:> writes:
>
> > I fixed it walking a bit more. For some reason, the citation @XXXX is
> read
> > as a (Str x)
> > value instead of a Cite value. Walking the tree and pattern matching
> solved
> > it.
>
> Perhaps because you're running your filter after
> pandoc-crossref, which would convert it to a Str?
>
> Yes, filters are definitely fun and not too hard.
> Good to publicize that!
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/f91cf9f6-8d38-43ac-b3a5-b21070c66e14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2368 bytes --]
prev parent reply other threads:[~2018-10-05 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 13:55 kiko.fernandez-1zs4UD6AkMk
[not found] ` <643e81d5-c3a2-4f68-927c-0500bb6ffd46-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-10-02 14:01 ` Robert Zenz
[not found] ` <5BB37A37.3050801-q1xk7osDwJUWQnjQ7V0W7w@public.gmane.org>
2018-10-02 14:03 ` Robert Zenz
2018-10-02 21:39 ` Kolen Cheung
[not found] ` <6d5f7166-099c-4fa7-92c9-b60146ea97a5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-10-03 13:56 ` kiko.fernandez-1zs4UD6AkMk
2018-10-04 8:21 ` kiko.fernandez-1zs4UD6AkMk
[not found] ` <e28b2c92-2f45-4c2a-9bb6-8084c2f95ad3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-10-04 16:22 ` John MacFarlane
[not found] ` <m2d0spu1eu.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-10-05 10:33 ` kiko.fernandez-1zs4UD6AkMk [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=f91cf9f6-8d38-43ac-b3a5-b21070c66e14@googlegroups.com \
--to=kiko.fernandez-1zs4ud6akmk@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).