From: Bastien <email@example.com>
To: "Thomas S. Dye" <firstname.lastname@example.org>
Cc: Org-mode <email@example.com>
Subject: Re: texinfo back-end won't export to INFO
Date: Tue, 18 Dec 2012 18:25:14 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Thomas S. Dye's message of "Sun, 11 Nov 2012 22:47:11 -1000")
firstname.lastname@example.org (Thomas S. Dye) writes:
> Export to INFO fails to produce an output file.
> Export to TEXI works. Running makeinfo on the texi file yields errors
> like this:
> /Users/dk/org/orgmanual//orgmanual.texi:171: `Exporting' has no Up field
> (perhaps incorrect sectioning?).
> If I run the texi file through (texinfo-all-menus-update), then makeinfo
> runs without error and produces an info file.
> Perhaps this step should be added to the texinfo back-end?
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?
next prev parent reply other threads:[~2012-12-18 17:25 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 [this message]
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
2012-12-18 21:54 ` Bastien
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 \
* 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).