From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Millar Subject: Re: [PATCH] Add catch-up all LaTeX errors Date: Wed, 26 Mar 2014 18:33:30 -0400 Message-ID: <533355BA.1030003@verizon.net> References: <87vc14i5wp.fsf@somewhere.org> <87siq5gh6w.fsf@somewhere.org> <87zjkdt3le.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58670) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSwOW-0002J3-1O for emacs-orgmode@gnu.org; Wed, 26 Mar 2014 18:34:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WSwON-0000vR-JR for emacs-orgmode@gnu.org; Wed, 26 Mar 2014 18:33:59 -0400 Received: from vms173009pub.verizon.net ([206.46.173.9]:23799) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSwON-0000vE-EJ for emacs-orgmode@gnu.org; Wed, 26 Mar 2014 18:33:51 -0400 Received: from [192.168.1.5] ([unknown] [70.209.136.61]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0N3200BD4ENVN700@vms173009.mailsrvcs.net> for emacs-orgmode@gnu.org; Wed, 26 Mar 2014 17:33:32 -0500 (CDT) In-reply-to: <87zjkdt3le.fsf@gmail.com> 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: emacs-orgmode@gnu.org, Nicolas Goaziou Nicolas Goaziou wrote: > > > Hello, > Nicholas and Francesco, > "Francesco Pizzolante" > writes: > >>> The issue is the fact that, when exporting to PDF, in some cases, Org tells >>> that the export has been done successfully while the PDF file has not been >>> produced! >>> >>> As an example, if you open the target PDF file with Adobe Reader and, in the >>> meantime, you export your Org file again to PDF, you'll see that Org will tell >>> you it's OK (Process Completed) while, if you look at the *Org PDF LaTeX >>> Output* buffer, you'll see an error such as: >>> >>> ! I can't write on file `toto.pdf'. >>> [...] >>> >>> The problem comes from the fact that Org just checks for a couple of error >>> messages (defined in org-latex-known-errors) and report it's OK if it doesn't >>> find those messages: > > Errors are not related to your problem. Actually, "ox-latex.el" uses > a rather weak check to know if process was successful or not: > > (if (not (file-exists-p pdffile)) > (error (concat (format "PDF file %s wasn't produced" pdffile) > (when errors (concat ": " errors)))) > ... > (message (concat "Process completed" > (if (not errors) "." (concat " with errors: " errors))))) > First, I have subsequent messages in this thread and the discussion. Should Nick's observation, that > IOW, it cannot tell the difference between a successful export and an > export failure with an already existing PDF also include the qualification that the existing PDF file is also opened at the time of the second export? I base this on Francesco's example above and the following. I usually export a subtree to LaTeX as PDF file and open. If I make small corrections to the subtree and export again, AND forget to close the PDF file that is already opened from the earlier export, Org reports a successful export; however, the "revised" exported PDF does not exist. (Also I use EXPORT_FILE_NAME: in PROPERTIES as the top of the subtree.) If I remember to close the first exported PDF, the revised subtree exports OK. I'm just curious, does the problem exist iff the pdf, that is to be replaced, is opened? Charlie Millar