From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: Asychronous export fails [8.3.2 (8.3.2-52-g6d0af5-elpa @ /home/rrt/.emacs.d/elpa/org-20151228/)] Date: Sun, 03 Jan 2016 20:53:47 +0100 Message-ID: <87k2nqqw1g.fsf@nicolasgoaziou.fr> References: <871t9zmx7e.fsf@sc3d.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51740) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFogy-0003NO-Oi for emacs-orgmode@gnu.org; Sun, 03 Jan 2016 14:51:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFogx-0007RH-Oz for emacs-orgmode@gnu.org; Sun, 03 Jan 2016 14:51:52 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:43920) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFogx-0007RD-JF for emacs-orgmode@gnu.org; Sun, 03 Jan 2016 14:51:51 -0500 In-Reply-To: <871t9zmx7e.fsf@sc3d.org> (Reuben Thomas's message of "Sat, 02 Jan 2016 22:29:57 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Reuben Thomas Cc: emacs-orgmode@gnu.org Hello, Reuben Thomas writes: > Remember to cover the basics, that is, what you expected to happen and > what in fact did happen. You don't know how to make a good report? See > > http://orgmode.org/manual/Feedback.html#Feedback > > Your bug report will be posted to the Org-mode mailing list. > ------------------------------------------------------------------------ > > With either 8.2.10 (as shipped with Emacs 24.4/5) or 20151228 (as > installed from ELPA), asychronous export to PDF via LaTeX fails unless I > have > > (setq org-export-async-debug nil) > > in my .emacs. Could you provide a backtrace of the error you're encountering? Also, if `org-export-async-debug' is non-nil, Org should leave an informative buffer somewhere with any error encountered on the other process. Regards, -- Nicolas Goaziou