From: Christian Moe <mail@christianmoe.com>
To: "A. Major" <andras.g.major@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results
Date: Thu, 08 Mar 2012 21:09:01 +0100 [thread overview]
Message-ID: <4F5911DD.6050805@christianmoe.com> (raw)
In-Reply-To: <loom.20120308T073456-970@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
On 3/8/12 7:38 AM, A. Major wrote:
> Thanks, but the "dir" PROPERTY appears to affect the target directory for
> babel's results, neither the HTML nor the PDF output are influenced that way.
Yes, that's why I said "this part of the problem".
> Combining BIND and the "dir" PROPERTY, I can get HTML and babel files in the
> right place, but not the PDF.
>
> Any other suggestions? :)
Yep. Change three characters in org-latex.el. Problem solved. Maybe. :)
The attached patch addresses a difference between the latex and html
exporters, enabling the user to choose a different output directory
for latex/PDF export by binding org-export-publishing directory, just
as was already possible for html export.
If there's a latex user following this thread who understands the ways
of the latex exporter, could you have a look to see that it doesn't
screw up anything else before I submit a properly formatted patch?
Yours,
Christian
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 03664b4..759fad4 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -870,7 +870,7 @@ when PUB-DIR is set, use this as the publishing
directory."
(concat
(file-name-as-directory
(or pub-dir
- (org-export-directory :LaTeX ext-plist)))
+ (org-export-directory :LaTeX opt-plist)))
(file-name-sans-extension
(or (and subtree-p
(org-entry-get rbeg "EXPORT_FILE_NAME" t))
[-- Attachment #2: org-latex.el.diff --]
[-- Type: text/plain, Size: 470 bytes --]
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 03664b4..759fad4 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -870,7 +870,7 @@ when PUB-DIR is set, use this as the publishing directory."
(concat
(file-name-as-directory
(or pub-dir
- (org-export-directory :LaTeX ext-plist)))
+ (org-export-directory :LaTeX opt-plist)))
(file-name-sans-extension
(or (and subtree-p
(org-entry-get rbeg "EXPORT_FILE_NAME" t))
next prev parent reply other threads:[~2012-03-08 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 12:38 BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results A. Major
2012-03-07 16:10 ` Myles English
2012-03-07 17:30 ` Christian Moe
2012-03-08 6:38 ` A. Major
2012-03-08 20:09 ` Christian Moe [this message]
2012-03-23 13:00 ` Bastien
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=4F5911DD.6050805@christianmoe.com \
--to=mail@christianmoe.com \
--cc=andras.g.major@gmail.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).