From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: problem with ox-pandoc export
Date: Fri, 03 Jul 2015 18:57:37 +0200 [thread overview]
Message-ID: <87pp49xjpa.fsf@gmx.us> (raw)
In-Reply-To: 871tgp2nvy.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Richard Lawrence <richard.lawrence@berkeley.edu> writes:
>
>> Rasmus <rasmus@gmx.us> writes:
>>
>>> I don't see it as reinventing the wheel. One example, does pandoc have
>>> something like the ox filters?
>>
>> It does; see e.g. http://pandoc.org/scripting.html
>>
>> Pandoc filters are actually more powerful than Org filters in most
>> cases, because they are AST transformations. Pattern matching makes it
>> convenient and practical in Haskell to just transform the part of the
>> tree you're interested in. And because the Pandoc data structure has a
>> JSON serialization format, filters can be written in just about any
>> language, not just Haskell.
>>
>> This is an nice system, IMHO, which has one big advantage: it is
>> possible to write complex filters (i.e., those that do more than just
>> simple string manipulation) in an output-agnostic way. Pandoc filters
>> can do things which are generally only possible or convenient to do in
>> Org by creating a derived backend, which isn't output-agnostic.
>
> For the record, you can do the same in Org with a parse tree filter.
> Other filters are meant to be less powerful but easier to write.
Not to mention the org-export-before filters if you want something that's
still "easy" and in org syntax.
Rasmus
--
Enough with the bla bla!
prev parent reply other threads:[~2015-07-03 16:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 12:59 problem with ox-pandoc export Alan Schmitt
2015-06-26 15:36 ` Nicolas Goaziou
2015-06-27 10:07 ` Alan Schmitt
2015-06-27 10:19 ` Alan Schmitt
2015-06-27 10:26 ` Nicolas Goaziou
2015-06-28 16:48 ` Alan Schmitt
2015-06-29 9:52 ` Alan Schmitt
2015-06-29 12:19 ` Nicolas Goaziou
2015-06-29 14:50 ` Alan Schmitt
2015-06-29 18:54 ` Nicolas Goaziou
2015-06-30 7:31 ` Alan Schmitt
2015-07-01 12:57 ` Nicolas Goaziou
2015-07-02 9:23 ` Sebastien Vauban
2015-07-02 11:34 ` Nicolas Goaziou
[not found] ` <87ioa2n68f.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-07-02 11:50 ` Sebastien Vauban
2015-07-02 12:02 ` Rasmus
2015-07-02 14:26 ` Fabrice Popineau
2015-07-02 14:35 ` Rasmus
2015-07-02 14:38 ` Fabrice Popineau
2015-07-07 15:22 ` Rasmus
2015-07-02 21:31 ` Nicolas Goaziou
2015-07-02 22:31 ` Rasmus
2015-07-03 10:23 ` Nicolas Goaziou
2015-07-03 16:37 ` Richard Lawrence
2015-07-03 16:42 ` Nicolas Goaziou
2015-07-03 16:57 ` Rasmus [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pp49xjpa.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).