From: tsd@tsdye.com (Thomas S. Dye)
To: Bastien <bzg@altern.org>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: texinfo back-end won't export to INFO
Date: Tue, 18 Dec 2012 08:19:00 -1000 [thread overview]
Message-ID: <m1wqwf2pgr.fsf@poto.westell.com> (raw)
In-Reply-To: <87mwxbe0hx.fsf@bzg.ath.cx> (Bastien's message of "Tue, 18 Dec 2012 18:25:14 +0100")
Aloha Bastien,
Bastien <bzg@altern.org> writes:
> Hi Thomas,
>
> tsd@tsdye.com (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?
IIUC, Jonathan Leeche-Pepin fixed this in org-e-texinfo.el a while back.
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
next prev parent reply other threads:[~2012-12-18 18:19 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 [this message]
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
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=m1wqwf2pgr.fsf@poto.westell.com \
--to=tsd@tsdye.com \
--cc=bzg@altern.org \
--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).