On Monday, 3 Oct 2016 at 17:08, Nick Dokos wrote:
> It's there even if there is an error (and arguably, that's the most useful
> case).
Yes, of course, if there is an error in the LaTeX.
My point was that org can fail to create the LaTeX and so the LaTeX to
PDF process doesn't take place at all
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
Nick Dokos writes:
> No, it should be present: it is created when you export to PDF through
> LaTeX (it is created by org-latex-compile which is called by
> org-latex-export-to-pdf). I just tried a (successful, but I don't
> think it matters) export and was able to visit it afterwards.
I found
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 behav
Julien Cubizolles writes:
> 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, it should be present: it is created when you expo
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 ?
Julien.
