From: Robert Klein <kleinrob@mpip-mainz.mpg.de>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Eric Schulte <eric.schulte@gmx.com>
Subject: Re: Publishing using the new exporter
Date: Tue, 09 Oct 2012 12:07:15 +0200 [thread overview]
Message-ID: <5073F753.4010209@mpip-mainz.mpg.de> (raw)
In-Reply-To: <50730F2B.5030902@mpip-mainz.mpg.de>
Hello,
On 10/08/2012 07:36 PM, Robert Klein wrote:
> Hallo,
>
> On 10/08/2012 06:49 PM, Nicolas Goaziou wrote:
>> Hello,
>>
>>
>> I don't think so, but I cannot reproduce your problem. Could you try
>> again in a fresh emacs, once back-ends you need have been required?
>>
>
> I re-installed the git-version of org-mode, required 'org-e-html and
> 'org-e-latex and exported from a fresh emacs. Issue 1 and 3 above are
> gone, but I still get empty images when calling org-e-publish from a
> buffer visiting a file outside the base-directory.
>
> I appended both a minimal .emacs and org file I used for the tests.
>
> Best regards
> Robert
>
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.
Best regards
Robert
next prev parent reply other threads:[~2012-10-09 10:07 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 [this message]
2012-10-10 16:59 ` Nicolas Goaziou
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=5073F753.4010209@mpip-mainz.mpg.de \
--to=kleinrob@mpip-mainz.mpg.de \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.com \
--cc=n.goaziou@gmail.com \
/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).