emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Wed, 10 Oct 2012 21:15:33 +0200	[thread overview]
Message-ID: <5075C955.3010408@mpip-mainz.mpg.de> (raw)
In-Reply-To: <87sj9m461v.fsf@gmail.com>

Hello,

On 10/10/2012 06:59 PM, Nicolas Goaziou wrote:
> 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,
>

I did some more tests and it seems the issue happens when Emacs is just 
started and nothing (much) done in it.

Test description below.

Best regards
Robert



* Setting up emacs and org-mode

** cleaning up emacs configuration
#+begin_src sh
# clean out .emacs.d
rm -rf ~/.emacs.d
# re-create and copy plantuml.jar
mkdir ~/.emacs.d
cp ~roklein/.emacs.d/plantuml.jar ~/.emacs.d/
#+end_src

** fetching org-mode git master
#+begin_src sh
mkdir $HOME/elisp && cd $HOME/elisp
git clone git://orgmode.org/org-mode.git
#+end_src

** local org configuration (local.mk)
#+begin_example :file ~/org-mode/local.mk
# Installation prefix
prefix  = /home/roklein/.emacs.d

# Where local lisp files go.
lispdir = $(prefix)/org-mode/lisp

# Where local data files go.
datadir = $(prefix)/org-mode/etc

# Where info files go.
infodir = $(prefix)/org-mode/info

# include files from contrib/lisp
ORG_ADD_CONTRIB = org-e-* org-md org-export org-contacts
#+end_example

** compile and install org-mode
#+begin_src sh
cd org-mode
vi local.mk  # see above
make
make install
#+end_src

This results in "Org-mode version 7.9.2 (release_7.9.2-432-g545166 @
   /home/emacs/.emacs.d/org-mode/lisp/)" from emacs M-x org-version.

* preparing the tests

Here I create ~/.emacs and ~/Documents/org/example/index.org as in the
former mail.

Further I create an image ~/example.png, simply containing the text
"FAIL!".

Touch  ~/Documents/org/other.org  (not ...txt)

* Test  preparation for each test

** cleaning up
    - closing emacs if open
    - executing the following commands
#+begin_src sh
cd
rm -rf public_html
rm Documents/org/example/index.tex*
rm Documents/org/example/index.pdf
rm Documents/org/example/example.png
rm .org-timestamps/*
#+end_src

* Test 1
   - Do test preparation as above
   - Start emacs from the command line.
   - M-x org-e-publish example
   - Have to type "yes" twice for executing plantuml.

* Result of Test 1
   - html export is Ok
   - pdf export has the "FAIL!" image I created in the home directory.

* Test 2
   - Do test preparation as above
   - Start emacs from the command line.
   - C-x C-f ~/Documents/org/example/index.org
   - M-x org-e-publish example
   - Have to type "yes" twice for executing plantuml.

* Result of Test 2
   - html export is Ok
   - pdf export is Ok

* Test 3
   - Do test preparation as above
   - Start emacs from the command line.
   - C-x C-f ~/Documents/org/example/index.org
   - C-x b *Gnu Emacs*
   - M-x org-e-publish example
   - Have to type "yes" twice for executing plantuml.

* Result of Test 3
   - html export is Ok
   - pdf export is Ok

* Test 4
   - Do test preparation as above
   - Start emacs from the command line.
   - C-x C-f ~/Documents/org/example/index.org
   - C-x C-f ~/Documents/org/other.txt
   - M-x org-e-publish example
   - Have to type "yes" twice for executing plantuml.

* Result of Test 4
   - html export is Ok
   - pdf export is Ok

* Test 5
   - Do test preparation as above
   - Start emacs from the command line.
   - C-x C-f ~/Documents/org/example/index.org
   - C-x C-f ~/Documents/org/other.txt
   - C-x C-s
   - M-x org-e-publish example
   - Have to type "yes" twice for executing plantuml.

* Result of Test 5
   - html export is Ok
   - pdf export is Ok

* Test 6
   - Change ~/.emacs to autoload a file ~/Documents/org/other.org
   - Start emacs from the command line.
   - (It has *Gnu Emacs* as front buffer)
   - M-x org-e-publish example
   - Have to type "yes" twice for executing plantuml.

* Result of Test 6
   - html export is Ok
   - pdf export has the "FAIL!" image I created in the home directory.

* Test 7
   - .emacs as in Test 6
   - Start emacs from the command line.
   - C-x C-f ~/Documents/org/example/index.org
   - M-x org-e-publish example
   - Have to type "yes" twice for executing plantuml.

* Result of Test 7
   - html export is Ok
   - pdf export is Ok

* Test 8
   - Change ~/.emacs to autoload a file ~/Documents/org/other.org
   - Start emacs from the command line.
   - C-x C-f ~/Documents/org/example/index.org
   - change buffer to other.org: C-f b other.org
   - M-x org-e-publish example
   - Have to type "yes" twice for executing plantuml.

* Result of Test 8
   - html export is Ok
   - pdf export is Ok

* Conclusion
   In these tests the issue only happens, when I start Emacs and
   publish without doing anything(much?)  else before publishing.

   Perhaps there is an issue with the setup and some stuff doesn't get
   initialized.

  reply	other threads:[~2012-10-10 19:15 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
2012-10-10 19:15                         ` Robert Klein [this message]
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=5075C955.3010408@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).