From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Slight change to asynchronous export
Date: Mon, 28 Oct 2013 18:39:40 +0100 [thread overview]
Message-ID: <8761shs3ab.fsf@Rainer.invalid> (raw)
In-Reply-To: 87fvrnawes.fsf@gmail.com
Nicolas Goaziou writes:
> At the moment, by default, external emacs process for asynchronous
> export is called with:
>
> /path/to/emacs -Q --batch -l org-export-async-init-file ... export stuff...
>
> where `org-export-async-init-file' defaults to `user-init-file'. It is,
> by default, not the same as calling "emacs", because of the "-Q".
That's a good thing, I'd say. There is a lot of stuff going on in init
files that you most likely don't want done when firing Emacs off in the
background. That is especially true of some site-init files that you
typically have no control over.
> I suggest allowing a nil (default) value for
> `org-export-async-init-file'. In that case, the command will become:
>
> /path/to/emacs --batch ... export stuff...
>
> If it is a file, it will be the same as before.
>
> WDYT?
If you don't make this the default then no harm is done, I guess.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2013-10-28 17:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 9:35 [RFC] Slight change to asynchronous export Nicolas Goaziou
2013-10-28 8:46 ` Sebastien Vauban
2013-10-28 9:04 ` Nicolas Goaziou
2013-10-29 10:43 ` Rasmus
2013-10-29 13:27 ` Nicolas Goaziou
2013-10-28 15:04 ` Carsten Dominik
2013-10-28 15:07 ` Aaron Ecay
2013-10-28 17:18 ` Nicolas Goaziou
2013-10-28 17:22 ` Aaron Ecay
2013-10-29 10:50 ` Rasmus
2013-10-28 17:39 ` Achim Gratz [this message]
2013-10-29 8:35 ` Nicolas Goaziou
2013-10-29 17:42 ` Rick Frankel
2013-10-30 8:27 ` Sebastien Vauban
2013-10-30 10:00 ` Nicolas Goaziou
2013-10-30 13:50 ` Rick Frankel
2013-10-31 10:23 ` Nicolas Goaziou
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=8761shs3ab.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).