emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Julian Gehring <julian.gehring@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Publish setup in file
Date: Tue, 12 Mar 2013 14:20:36 +0100	[thread overview]
Message-ID: <87y5ds3gbf.fsf@bzg.ath.cx> (raw)
In-Reply-To: <khik3b$tog$1@ger.gmane.org> (Julian Gehring's message of "Sun, 10 Mar 2013 19:40:46 +0100")

Hi Julian,

Julian Gehring <julian.gehring@gmail.com> writes:

> Is there a way to specify publishing options (e.g. the location) at the
> level of the file to be published, instead doing this globally in the
> =.emacs= file?

The publication process thinks in terms of "projects", not in terms of
files, so you need to organize your files and projects in a way that
makes :publishing-directory do the right thing.

If we alleviate this limitation, we will end up with option keywords
like #+HTML_PUB_DIR and #+LaTeX_PUB_DIR which will then override the
:publishing-directory option, but this would perhaps be confusing.



      reply	other threads:[~2013-03-12 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10 18:40 Publish setup in file Julian Gehring
2013-03-12 13:20 ` 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=87y5ds3gbf.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=julian.gehring@gmail.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).