emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Org-mode <emacs-orgmode@gnu.org>, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: texinfo back-end won't export to INFO
Date: Tue, 18 Dec 2012 21:24:06 +0100	[thread overview]
Message-ID: <87obhrjehl.fsf@gmail.com> (raw)
In-Reply-To: <87ehinb36h.fsf@bzg.ath.cx> (Bastien's message of "Tue, 18 Dec 2012 19:55:34 +0100")

Bastien <bzg@altern.org> writes:

>> A filter function requires three arguments.
> ... so that's where complexity comes from.  I'm afraid you'll just 
> scare away many users with these three arguments.  
> What do you think?

Using a hook or a filter requires to write a function in most cases.
I don't think that a person able to write such a function would cringe
in front of a function of three arguments (you don't even have to use
them all).

Filters are applied on something (often a string). That something is the
first argument. Also, filters are probably very dependant on the
back-end used. That is the second argument. Eventually, it may be useful
to know which options were active at the time of export. This is the
third argument.

I can remove the last argument, bringing down the sum of arguments to 2.
Should I?


Nicolas Goaziou

  reply	other threads:[~2012-12-18 20:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12  8:47 texinfo back-end won't export to INFO Thomas S. Dye
2012-12-18 17:25 ` Bastien
2012-12-18 18:19   ` Thomas S. Dye
2012-12-18 18:52     ` org-export-after-rendering-hook for the new exporter? (was: texinfo back-end won't export to INFO) Bastien
2012-12-18 18:20   ` texinfo back-end won't export to INFO Nicolas Goaziou
2012-12-18 18:55     ` Bastien
2012-12-18 20:24       ` Nicolas Goaziou [this message]
2012-12-18 21:54         ` Bastien

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:

  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=87obhrjehl.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.com \


* 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


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).