emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Robert Klein <kleinrob@mpip-mainz.mpg.de>
Cc: emacs-orgmode@gnu.org, Eric Schulte <eric.schulte@gmx.com>
Subject: Re: Publishing using the new exporter
Date: Wed, 10 Oct 2012 18:59:08 +0200	[thread overview]
Message-ID: <87sj9m461v.fsf@gmail.com> (raw)
In-Reply-To: <5073F753.4010209@mpip-mainz.mpg.de> (Robert Klein's message of "Tue, 09 Oct 2012 12:07:15 +0200")

Hello,

Robert Klein <kleinrob@mpip-mainz.mpg.de> writes:

> I got i working with this patch:
>
> diff --git a/contrib/lisp/org-e-latex.el b/contrib/lisp/org-e-latex.el
> index 80b8ddb..2d4ad35 100644
> --- a/contrib/lisp/org-e-latex.el
> +++ b/contrib/lisp/org-e-latex.el
> @@ -2670,6 +2670,7 @@ Return PDF file name or an error if it couldn't
> be produced."
>    (let* ((wconfig (current-window-configuration))
>          (texfile (file-truename texfile))
>          (base (file-name-sans-extension texfile))
> +        (default-directory base)
>          errors)
>      (message (format "Processing LaTeX file %s ..." texfile))
>      (unwind-protect
>
>
> After reading a bit in the emacs lisp reference manual I knew the
> issue is something with default-directory.  Then I examined the code
> of the old exporter and looked for a "similar" place in the new
> exporter, happily finding a 'let*( ...'.   Not sure, this is Ok or
> even the right place.  Just happy at the moment it does work.
>
> Both cases (buffer visited in base-directory and not in
> base-directory) work with the change.

I still cannot reproduce the problem, even with your recipe. Could you
double-check it?

Also, there's nothing in `org-e-latex-compile' that should depend on
default-directory anyway.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2012-10-10 17:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24  9:57 Publishing using the new exporter Robert Klein
2012-09-24 10:25 ` Nicolas Goaziou
2012-09-24 15:57   ` Nick Dokos
2012-09-24 17:25     ` Achim Gratz
2012-09-24 17:27   ` Robert Klein
2012-09-25  7:16     ` Robert Klein
2012-09-25 10:58       ` Nicolas Goaziou
2012-09-25 20:54       ` Nicolas Goaziou
2012-10-06 11:17     ` Nicolas Goaziou
2012-10-06 14:52       ` Robert Klein
2012-10-06 17:48         ` Nicolas Goaziou
2012-10-07 13:21           ` Robert Klein
2012-10-08 12:55             ` Nicolas Goaziou
2012-10-08 16:05               ` Robert Klein
2012-10-08 16:49                 ` Nicolas Goaziou
2012-10-08 17:36                   ` Robert Klein
2012-10-08 17:46                     ` Suvayu Ali
2012-10-09  5:06                       ` Robert Klein
2012-10-09 10:07                     ` Robert Klein
2012-10-10 16:59                       ` Nicolas Goaziou [this message]
2012-10-10 19:15                         ` Robert Klein
2012-10-11 21:55                           ` Nicolas Goaziou
2012-10-15  9:35                             ` Robert Klein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sj9m461v.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric.schulte@gmx.com \
    --cc=kleinrob@mpip-mainz.mpg.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).