Hello,
Achim Gratz strom...@nexgo.de writes:
Sadly not. Somewhere in org-e-latex (I think) the path is made absolute
again.
I'll have a look at it later unless you find it earlier.
By default, commands from `org-e-latex-pdf-process' use %f place
holder, which is the absolute file name.
Nicolas Goaziou n.goaziou at gmail.com writes:
By default, commands from `org-e-latex-pdf-process' use %f place
holder, which is the absolute file name. You may want to use %b (and
a recent Org pull) instead.
I've pulled again and used texi2dvi from the value menu and all is well now.
Thanks.
Nicolas Goaziou n.goaziou at gmail.com writes:
The new exporter fires off LaTeX with an absolute path for the file to
export. If you happen to use a native Emacs, but the LaTeX from Cygwin
that will fail because it expects a POSIX path. Would it be possible to
change things so that a
The new exporter fires off LaTeX with an absolute path for the file to
export. If you happen to use a native Emacs, but the LaTeX from Cygwin
that will fail because it expects a POSIX path. Would it be possible to
change things so that a relative path is used as in the old exporter (or
better
Hello,
Achim Gratz strom...@nexgo.de writes:
The new exporter fires off LaTeX with an absolute path for the file to
export. If you happen to use a native Emacs, but the LaTeX from Cygwin
that will fail because it expects a POSIX path. Would it be possible to
change things so that a
Nicolas Goaziou writes:
The new exporter fires off LaTeX with an absolute path for the file to
export. If you happen to use a native Emacs, but the LaTeX from Cygwin
that will fail because it expects a POSIX path. Would it be possible to
change things so that a relative path is used as in
Hi Nicolas,
Nicolas Goaziou wrote:
Achim Gratz strom...@nexgo.de writes:
The new exporter fires off LaTeX with an absolute path for the file to
export. If you happen to use a native Emacs, but the LaTeX from Cygwin that
will fail because it expects a POSIX path. Would it be possible to
