emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: mail@christianmoe.com
Cc: "A. Major" <andras.g.major@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results
Date: Fri, 23 Mar 2012 14:00:24 +0100	[thread overview]
Message-ID: <87iphvmpzr.fsf@gnu.org> (raw)
In-Reply-To: <4F5911DD.6050805@christianmoe.com> (Christian Moe's message of "Thu, 08 Mar 2012 21:09:01 +0100")


I fixed this bug.

Christian Moe <mail@christianmoe.com> writes:

> 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. :)

You showed the direction -- thanks!  The right fix is to use
org-export-latex-options-plist, which is initialized by combining
opt-plist (general options for publishing) and ext-plist (local LaTeX
options for publishing.)



      reply	other threads:[~2012-03-23 12:59 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
2012-03-23 13:00         ` Bastien [this message]

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:

  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=87iphvmpzr.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=andras.g.major@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \


* 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


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).