emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <cdominik@newartisans.com>
To: emacs-orgmode@gnu.org
Subject: [Accepted] Re: Problem when exporting to PDF to a different directory
Date: Fri, 13 Aug 2010 22:44:29 +0200 (CEST)	[thread overview]
Message-ID: <20100813204429.4570A1AEB719@carsten-dominiks-macbook-pro.local> (raw)
In-Reply-To: AANLkTikA0=vUhyavQ7g12uJyQRJa+xJzE-m60zE95PT2@mail.gmail.com

Patch 203 (http://patchwork.newartisans.com/patch/203/) is now "Accepted".

Maintainer comment: No comment

This relates to the following submission:

http://mid.gmane.org/%3CAANLkTikA0%3DvUhyavQ7g12uJyQRJa%2BxJzE-m60zE95PT2%40mail.gmail.com%3E

Here is the original message containing the patch:

> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: Re: [Orgmode] Problem when exporting to PDF to a different directory
> Date: Sat, 07 Aug 2010 14:00:49 -0000
> From: Noorul Islam <noorul@noorul.com>
> X-Patchwork-Id: 203
> Message-Id: <AANLkTikA0=vUhyavQ7g12uJyQRJa+xJzE-m60zE95PT2@mail.gmail.com>
> To: Manuel Amador <amador.manuel@gmail.com>
> Cc: emacs-orgmode@gnu.org
> 
> On Wed, Aug 4, 2010 at 1:26 AM, Manuel Amador <amador.manuel@gmail.com>wrote:
> 
> > Hi everybody,
> >
> > I am running into the following issue.
> >
> > I would like to export certain subtrees of an org file to a particular
> > directory. I set the export property as follows:
> >
> > * Test 1
> >   :PROPERTIES:
> >   :EXPORT_FILE_NAME: some_directory/some_name
> >   :END:
> >
> >
> > When I try exporting the above subtree as a pdf (say for example, by
> > running
> > C-c C-e 1 d), the .tex file is created in the appropriate target directory,
> > but
> > the .pdf file is created in the current directory (while emacs mistakenly
> > reports that the pdf was not created). Is there a way to get this to work
> > correctly?
> >
> >
> The following patch solves this problem. Actually html export has no issues
> with this.
> 
> * lisp/org-latex.el:
>   + Modify the custom variable org-latex-to-pdf-process to include
> -output-directory option for
>      the command pdflatex.
>   + org-export-as-pdf()
>      Give some respect to  EXPORT_FILE_NAME if it has path elements.
>      Modified some of the messages to include the file name.
> 
> Thanks and Regards
> Noorul
> 
> 
> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
> index 056f1b3..2e42399 100644
> --- a/lisp/org-latex.el
> +++ b/lisp/org-latex.el
> @@ -451,12 +451,13 @@ allowed.  The default we use here encompasses both."
>    :group 'org-export)
>  
>  (defcustom org-latex-to-pdf-process
> -  '("pdflatex -interaction nonstopmode %s"
> -    "pdflatex -interaction nonstopmode %s")
> +  '("pdflatex -interaction nonstopmode -output-directory %o %f"
> +    "pdflatex -interaction nonstopmode -output-directory %o %f")
>    "Commands to process a LaTeX file to a PDF file.
>  This is a list of strings, each of them will be given to the shell
> -as a command.  %s in the command will be replaced by the full file name, %b
> -by the file base name (i.e. without extension).
> +as a command.  %f in the command will be replaced by the full file name, %b
> +by the file base name (i.e. without extension) and %o by the base directory
> +of the file.
>  The reason why this is a list is that it usually takes several runs of
>  pdflatex, maybe mixed with a call to bibtex.  Org does not have a clever
>  mechanism to detect which of these commands have to be run to get to a stable
> @@ -840,9 +841,10 @@ when PUB-DIR is set, use this as the publishing directory."
>  		     (save-excursion
>  		       (goto-char (point-min))
>  		       (re-search-forward "\\\\bibliography{" nil t))))
> -	 cmd)
> +	 cmd output-dir)
>      (with-current-buffer outbuf (erase-buffer))
> -    (message "Processing LaTeX file...")
> +    (message (concat "Processing LaTeX file " file "..."))
> +    (setq output-dir (file-name-directory file))
>      (if (and cmds (symbolp cmds))
>  	(funcall cmds (shell-quote-argument file))
>        (while cmds
> @@ -852,15 +854,20 @@ when PUB-DIR is set, use this as the publishing directory."
>  		     (save-match-data
>  		       (shell-quote-argument base))
>  		     t t cmd)))
> -	(while (string-match "%s" cmd)
> +	(while (string-match "%f" cmd)
>  	  (setq cmd (replace-match
>  		     (save-match-data
>  		       (shell-quote-argument file))
>  		     t t cmd)))
> +	(while (string-match "%o" cmd)
> +	  (setq cmd (replace-match
> +		     (save-match-data
> +		       (shell-quote-argument output-dir))
> +		     t t cmd)))
>  	(shell-command cmd outbuf outbuf)))
> -    (message "Processing LaTeX file...done")
> +    (message (concat "Processing LaTeX file " file "...done"))
>      (if (not (file-exists-p pdffile))
> -	(error "PDF file was not produced")
> +	(error (concat "PDF file " pdffile " was not produced"))
>        (set-window-configuration wconfig)
>        (when org-export-pdf-remove-logfiles
>  	(dolist (ext org-export-pdf-logfiles)
> 

  reply	other threads:[~2010-08-16 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 19:56 Problem when exporting to PDF to a different directory Manuel Amador
2010-08-07  9:00 ` [PATCH] " Noorul Islam
2010-08-13 20:44   ` Carsten Dominik [this message]
2010-08-08 12:26 ` David Maus

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=20100813204429.4570A1AEB719@carsten-dominiks-macbook-pro.local \
    --to=cdominik@newartisans.com \
    --cc=emacs-orgmode@gnu.org \
    /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).