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 19:20:31 +0100	[thread overview]
Message-ID: <8738z3kys0.fsf@gmail.com> (raw)
In-Reply-To: <87mwxbe0hx.fsf@bzg.ath.cx> (Bastien's message of "Tue, 18 Dec 2012 18:25:14 +0100")

Hello,

Bastien <bzg@altern.org> writes:

> I think this calls for a new variable `org-export-after-rendering-hook'
> which will operate after the final stage of the export process, in the
> export buffer.  Filters are fine but their complexity is not useful here.
>
> Then we could add 'texinfo-all-menus-update to this hook.
>
> Nicolas, what do you think?

There is no such thing as an "export buffer" in the new exporter,
`org-export-as' produces a string.

Though, there is `org-export-filter-final-output-functions', which will
operate on the last string produced by `org-export-as'. You may create
a function that will insert that string in a buffer, apply
`texinfo-all-menus-update' and call `buffer-string', and add it to that
filter set.

Note that complexity of filters is the same as hook: you add functions
to a list. A filter function requires three arguments.


Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2012-12-18 18:24 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   ` Nicolas Goaziou [this message]
2012-12-18 18:55     ` texinfo back-end won't export to INFO Bastien
2012-12-18 20:24       ` Nicolas Goaziou
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:
  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=8738z3kys0.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.com \
    /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).