From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Slight change to asynchronous export
Date: Mon, 28 Oct 2013 18:18:31 +0100 [thread overview]
Message-ID: <87ppqp9uvs.fsf@gmail.com> (raw)
In-Reply-To: <87li1d1ljp.fsf@gmail.com> (Aaron Ecay's message of "Mon, 28 Oct 2013 11:07:22 -0400")
Hello,
Aaron Ecay <aaronecay@gmail.com> writes:
> My init.el file does (server-start), and also opens all the buffers
> (usually 100+) I had opened the last time I quit emacs (by using emacs’s
> included desktop library). The buffers in turn spawn child processes
> (aspell, some python IDE-ish autocomplete server, ...) I think these
> things are relatively common in init.el files, but not things that
> should be done by the async export process. Other examples might
> include gnus/other email/rss fetching, or automatic update of installed
> elpa packages.
>
> Of course this would not be an issue for me in particular, but I think
> it would be very easy for a user to get unwanted results.
At the moment, default configuration will load init.el (or an
equivalent) so my proposal is not different in that regard.
> I guess you want to make it so that users don’t have to configure async
> export (beyond just flipping it on) in order to use it.
I want the default value to be less surprising, even though I strongly
encourage users to customize `org-export-async-init-file'.
> But I don’t know if there is a sensible way to parcel out benign bits
> of initialization code from dangerous ones without user intervention.
I don't know either, and that is well out of the scope of my proposal.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-10-28 17:18 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 [this message]
2013-10-28 17:22 ` Aaron Ecay
2013-10-29 10:50 ` Rasmus
2013-10-28 17:39 ` Achim Gratz
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=87ppqp9uvs.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--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).