In my case the rm does generate an error, but the process doesn't stop.
On 12/4/10 3:28 PM, Jeff Horn wrote:
> Small problem: if the file doesn't exist, rm fails with error, which
> stops the process (the PDF file is not produced). This happens if I
> create a new source file in my project.
>
> O
Thanks for the help. I'm not really sure what's going on. A PDF file
is produced in my source directory, but not in my output directory. I
receive an error message saying the PDF file was not produced.
I didn't realize the customize menu had many different processes in
the value menu. I wanted som
On Sat, Dec 04, 2010 at 03:28:30PM -0500, Jeff Horn wrote:
> On Sat, Dec 4, 2010 at 3:22 PM, Jeff Horn wrote:
> > On Sat, Dec 4, 2010 at 3:20 PM, Mike McLean wrote:
> >> I solve this with a forced remove:
> >>
> >> (setq org-latex-to-pdf-process (quote ("rm %b.pdf" "texi2dvi -p -b -c -V
> >> %f")
Small problem: if the file doesn't exist, rm fails with error, which
stops the process (the PDF file is not produced). This happens if I
create a new source file in my project.
On Sat, Dec 4, 2010 at 3:22 PM, Jeff Horn wrote:
> On Sat, Dec 4, 2010 at 3:20 PM, Mike McLean wrote:
>> I solve this w
On Sat, Dec 4, 2010 at 3:20 PM, Mike McLean wrote:
> I solve this with a forced remove:
>
> (setq org-latex-to-pdf-process (quote ("rm %b.pdf" "texi2dvi -p -b -c -V
> %f")))
Nice! Very clever. Thanks for the tip! (CC-ing to the list, hope that's OK)
--
Jeffrey Horn
Graduate Lecturer and PhD Stu
Just a heads up: it looks like using texi2dvi for
org-latex-to-pdf-process will not recompile a tex file in certain
cases. I have different output and source directories, and when I
publish a changed org file, texi2dvi appears to not process a tex file
when the pdf is already in the output director
