From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [ANN] Asynchronous export for new exporter
Date: Thu, 13 Dec 2012 09:13:44 -1000 [thread overview]
Message-ID: <m1bodxg3yv.fsf@poto.myhome.westell.com> (raw)
In-Reply-To: <87mwxic855.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 13 Dec 2012 15:57:10 +0100")
Aloha Nicolas,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> New (experimental) exporter has now support for asynchronous export.
> Every type of export is supported (subtree, to a buffer, visible part
> only...).
>
> When produced, results are listed in the Export Stack (they will never
> make a buffer pop or call an external application). The stack can be
> accessed from the dispatcher interface, by calling dispatcher with
> a double C-u argument, or directly with `org-export-stack'.
>
> From there, output results can be viewed or removed from the stack.
> Removing a result from the stack only removes it from view. No file is
> deleted, no buffer is killed.
Move point to the result and press 'd'.
The age column is a real help here.
>
> You may want to tweak `org-export-in-background' and
> `org-export-async-init-file'. You can also toggle
> `org-export-async-debug' for debugging purposes.
>
> Feedback welcome.
Wow! This is a huge improvement. It is going to change my work rhythm.
I tangle the initialization file from my document. Can you show me how
to configure asynchronous export to run org-babel-tangle-file before
export to insure that the initialization file is always up-to-date?
Thanks for your good work.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2012-12-13 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 14:57 [ANN] Asynchronous export for new exporter Nicolas Goaziou
2012-12-13 17:38 ` Alan Schmitt
2012-12-13 19:13 ` Thomas S. Dye [this message]
2012-12-14 19:43 ` Nicolas Goaziou
2012-12-14 21:21 ` Thomas S. Dye
2012-12-30 8:32 ` Julien Cubizolles
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=m1bodxg3yv.fsf@poto.myhome.westell.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.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).