On Thu, 07 Oct 2010 10:43:21 +0200, Sébastien Vauban wrote: > > Hi Eric, > > Eric S Fraga wrote: > > As far as I know, there is nothing out of the ordinary with my paths etc > > (please note that the /.../ above was an edit on my part to hide a rather > > long path). Any hints as to what I can do to explore this would be most > > helpful. How can I get a trace on what texi2dvi is doing? (sh -v > > /usr/bin/texi2dvi?) > > I tried: > > #+begin_src emacs-lisp > (setq org-latex-to-pdf-process '("sh -v -x texi2dvi -p -b -c -V %f")) > #+end_src > > and only see the following in *Messages*: You can see the full output in the special buffer org creates: : *Org PDF LaTeX Output* All the output from the actual commands, such as the following, is placed in this buffer. Very useful for when there are problems with the latex. ,---- | This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) | restricted \write18 enabled. | entering extended mode | (/home/ucecesf/s/teaching/cape/lectures/matlab.tex | LaTeX2e <2009/09/24> | Babel and hyphenation patterns for english, usenglishmax, dumylang, noh | yphenation, loaded. | (/usr/share/texmf/tex/latex/beamer/base/beamer.cls | (/usr/share/texmf/tex/latex/beamer/base/beamerbasercs.sty) `---- This is different from the messages generated by the elisp code which appear in *Messages*.