From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Filter with arguments
Date: Fri, 6 Jan 2017 12:46:47 +0100 [thread overview]
Message-ID: <20170106114647.GG791@Administrateurs-iMac-3.local> (raw)
In-Reply-To: <e8cf9c92-7aa7-4841-85d0-7464c771cf6e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
This is a pretty common request. A couple of complications:
1. Pandoc calls each filter with one argument, the name of
the output format. (Filters thus have access to this.)
If we allowed `-F "pantable -t csv"`, how would this work?
Would pandoc call `pantable latex -t csv`? Would the filter
be expecting this?
2. We'd get a quoted argument like `"pantable -t csv"` as a
single string from the environment. So pandoc would have to
do its own parsing of this string into a command, options and
arguments. This is tricky. Maybe some people are already
using filters with spaces in them, like `-F "My Cool Filter.py".
This kind of thing would break if pandoc assumed that the
command was "My" and "Cool" an argument.
+++ Kolen Cheung [Jan 05 17 20:32 ]:
> Currently, if one need to pass arguments to a filter, one need to pipe
> it through.
>
> It would be convenient in some cases to allow passing argument to
> filters. e.g.
>pandoc -F "pantable -t csv" -s -o example.tex example.md
># which is equiv. to
>pandoc -t json -s example.md | pantable -t csv | pandoc -f json -s -o example.te
>x
>
> To elaborate a little bit further: I want to write a filter that at the
> same time do:
> 1. convert code block to table
> 2. convert pandoc tables to code block, potentially with different
> output code formats (e.g. csv, yaml, json, etc. or even other kinds
> e.g. HTML, Div with CSS table, etc.)
> 3. standalone cli. i.e. not a filter
>
> Right now (1) and (2) are mutually exclusive and has to be split into 2
> filters. (1) and (3) can potentially be written in the same executable,
> but it is uglier and pointless to do so without including (2).
>
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/e8cf9c92-7aa7-4841-
> 85d0-7464c771cf6e%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/e8cf9c92-7aa7-4841-85d0-7464c771cf6e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
--
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/20170106114647.GG791%40Administrateurs-iMac-3.local.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-01-06 11:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 4:32 [Feature Request] " Kolen Cheung
[not found] ` <e8cf9c92-7aa7-4841-85d0-7464c771cf6e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-06 11:46 ` John MacFarlane [this message]
[not found] ` <20170106114647.GG791-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2017-01-06 12:27 ` Joost Kremers
[not found] ` <8760ls8jby.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2017-01-06 12:58 ` John MacFarlane
[not found] ` <20170106125852.GA1662-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2017-01-06 18:32 ` BPJ
[not found] ` <CADAJKhCPn81DsWpzWSQHv59ii+SLXmz4Ww5ru1mSmP4eRQozow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-06 18:42 ` Matthew Pickering
[not found] ` <CALuQ0m8Jx2N_nKKOL5i5pNM9houf_iUe2Z54uWeajm2oVEZW5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-06 19:47 ` BPJ
2017-01-06 21:11 ` John MacFarlane
[not found] ` <20170106211115.GA30105-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2017-01-06 21:36 ` BPJ
2017-01-08 19:40 ` Joost Kremers
2017-01-06 23:10 ` Kolen Cheung
[not found] ` <1239e0f1-2538-4781-8a75-90c59f86aabc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-07 19:05 ` BP Jonsson
[not found] ` <c21c773d-c958-2e55-725d-90863f5f9792-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-07 20:51 ` Kolen Cheung
[not found] ` <de2e97b1-17a4-4f70-8c17-b3cd960dceb2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-07 22:53 ` BP Jonsson
[not found] ` <CAFC_yuTR=2UQZPN4EFbKTCOAwR9tOoS1+sYy5rLRViNo908s-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-08 9:09 ` John MacFarlane
[not found] ` <CADAJKhAwBq+mxsimD83aefMEUCm025i5QaNvfpGBzrAWrB7atQ@mail.gmail.com>
[not found] ` <CADAJKhACOpd-yQHTBTrL4VbCg8zyGiJX7WwECsifGtihbyyzCA@mail.gmail.com>
[not found] ` <CADAJKhACOpd-yQHTBTrL4VbCg8zyGiJX7WwECsifGtihbyyzCA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-08 11:21 ` Melroch
2017-01-08 20:51 ` [Feature Request] " Kolen Cheung
[not found] ` <434dc10f-02a1-4bbc-a41c-3a29398ca635-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-09 11:26 ` BP Jonsson
[not found] ` <CAFC_yuRuuDDfbok7Gds-kdj_ySqvpF0psnTUn0-TRvdEhRUs+Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-06 23:33 ` Kolen Cheung
2018-06-20 14:58 ` Peter Zagubisalo
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=20170106114647.GG791@Administrateurs-iMac-3.local \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).