From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: =?UTF-8?B?UmU6IElzIHRoZXJlIGEgKk9yZyBQREYgTGFUZVggT3V0cHV0KiBi?= =?UTF-8?B?dWZmZXLCoD8=?= Date: Mon, 03 Oct 2016 13:08:25 -0400 Message-ID: <87d1jhs6ly.fsf@gmail.com> References: <55929700b6fd4b07ac0d3c7ad1d328f8@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> <87wphstfq0.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49491) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1br6jV-0006Uf-8g for emacs-orgmode@gnu.org; Mon, 03 Oct 2016 13:08:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1br6jP-000615-Cb for emacs-orgmode@gnu.org; Mon, 03 Oct 2016 13:08:52 -0400 Received: from [195.159.176.226] (port=36556 helo=blaine.gmane.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1br6jP-0005z7-5e for emacs-orgmode@gnu.org; Mon, 03 Oct 2016 13:08:47 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1br6jC-0006Sa-EI for emacs-orgmode@gnu.org; Mon, 03 Oct 2016 19:08:34 +0200 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" To: emacs-orgmode@gnu.org Eric S Fraga writes: > On Friday, 30 Sep 2016 at 21:09, Julien Cubizolles wrote: >> When an export from org to pdf fails, the error message refers to a *Org >> PDF LaTeX Output* buffer that doesn't seem to have been created on my >> setup. Is it an old message from a previous behaviour long goneĀ ? > > No, this is current behaviour. The buffer should definitely be created > but probably only if the org is exported to LaTeX without error. It could > be the exporter is failing before it attempts to compile the LaTeX into > PDF. Check your messages (C-h e)? Typical error that causes the first > step to fail would be dangling links, for instance. It's there even if there is an error (and arguably, that's the most useful case). But I didn't try the async case which seems to cause the problem that the OP ran into. -- Nick