Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-28 Thread Sebastien Vauban
Nicolas Goaziou wrote: > Sebastien Vauban > writes: > >> Isn't `orgfile' equal to `org-babel-exp-reference-buffer' in >> `org-latex-compile'? > > No, `org-babel-exp-reference-buffer' is a temporary buffer attached to > no file. It cannot help to find original file. OK. From reading the docstring,

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-28 Thread Nicolas Goaziou
Hello, Sebastien Vauban writes: > Isn't `orgfile' equal to `org-babel-exp-reference-buffer' in > `org-latex-compile'? No, `org-babel-exp-reference-buffer' is a temporary buffer attached to no file. It cannot help to find original file. Regards, -- Nicolas Goaziou

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-28 Thread Francesco Pizzolante
Hi Marcin, > This is rather a workaround, but don't use Adobe Reader, use any other > PDF viewer instead. (IIRC, there's also a workaround that makes Adobe > Reader behave correctly, i.e. not lock the pdf file, but I can't find > it now. See here, for example: > http://stackoverflow.com/question

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-27 Thread Marcin Borkowski
Dnia 2014-03-26, o godz. 18:33:30 Charles Millar napisał(a): > 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? This is rather a workaround, but don't use Adobe Reade

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-27 Thread Francesco Pizzolante
Hi Charles, > 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 PD

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-27 Thread Sebastien Vauban
Hello, Nicolas Goaziou wrote: > Sebastien Vauban writes: > >> FWIW, I'm using this in some export code I have: >> >> (let* ((orgfile (buffer-file-name)) >> (base-name (file-name-base orgfile)) >> (htmlfile (concat base-name ".html")) >> (pdffile (concat

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-27 Thread Francesco Pizzolante
Hi Nicolas, >>> IOW, it cannot tell the difference between a successful export and an >>> export failure with an already existing PDFFILE. >> >> This is not true as this code checks for the `errors' variable in all >> cases. With an already existing PDFFILE, you will end up with this >> message:

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-27 Thread Nicolas Goaziou
Hello, Sebastien Vauban writes: > FWIW, I'm using this in some export code I have: > > (let* ((orgfile (buffer-file-name)) > (base-name (file-name-base orgfile)) > (htmlfile (concat base-name ".html")) > (pdffile (concat base-name ".pdf"))) >

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-26 Thread Charles Millar
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

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-26 Thread Sebastien Vauban
Nicolas Goaziou wrote: > "Francesco Pizzolante" writes: > >>> IOW, it cannot tell the difference between a successful export and an >>> export failure with an already existing PDFFILE. >> >> This is not true as this code checks for the `errors' variable in all >> cases. With an already existing PD

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-26 Thread Nicolas Goaziou
"Francesco Pizzolante" writes: >> IOW, it cannot tell the difference between a successful export and an >> export failure with an already existing PDFFILE. > > This is not true as this code checks for the `errors' variable in all > cases. With an already existing PDFFILE, you will end up with t

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-26 Thread Francesco Pizzolante
Hi Nicolas, Thanks for your answer. >>> 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* bu

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-26 Thread Nicolas Goaziou
Hello, "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 >>

Re: [O] [PATCH] Add catch-up all LaTeX errors

2014-03-26 Thread Francesco Pizzolante
Hi, May I bump up this thread? Thanks for your help. Regards, Francesco "Francesco Pizzolante" wrote: > Hi, > > This is not a definitive patch. It's just a first step in getting a better > one. > > The issue is the fact that, when exporting to PDF, in some cases, Org tells > that the export h

[O] [PATCH] Add catch-up all LaTeX errors

2013-10-11 Thread Francesco Pizzolante
Hi, This is not a definitive patch. It's just a first step in getting a better one. 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