From: Bastien Guerry <email@example.com>
Subject: [Accepted] Variable publishing-directory? (resent with patch as attachment)
Date: Sat, 22 Oct 2011 10:41:25 +0200 (CEST) [thread overview]
Message-ID: <20111022084125.9E737A976@myhost.localdomain> (raw)
Patch 895 (http://patchwork.newartisans.com/patch/895/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] Variable publishing-directory? (resent with patch as attachment)
> Date: Thu, 18 Aug 2011 13:17:56 -0000
> From: Kai Tetzlaff <firstname.lastname@example.org>
> X-Patchwork-Id: 895
> Message-Id: <email@example.com>
> To: firstname.lastname@example.org
> Bastien <email@example.com> writes:
> Hi Bastien,
> > The patch looks good but I'd like to understand it better.
> > Can you send an example configuration working with your patch?
> In org-publish-project-alist, i have HTML publishing projects which
> should be published to different target directories depending on e.g.
> where emacs is running (which i determine in my init files using the MAC
> address of the default GW, the name the machine, ...).
> Here is an example: At home, i publish to a local directory
> (:publishing-directory "~/tmp/publish-test") but at work i would like to
> publish directly to a webserver (:publishing-directory
> "/plinkx:doxydoc:~/public_html/publish-test" - this is on w32, using
> tramps PuTTY/plink). To avoid having to change the definition of the
> publishing project when i change locations i would like to construct the
> actual value of :publishing-directory by calling a function:
> :base-directory "~/Documents/Work/RS"
> :recursive t
> :base-extension "org"
> :exclude-tags ("intern")
> :publishing-directory '(expand-file-name "publish-test" kt:org-default-publishing-dir)
> :publishing-function org-publish-org-to-html)
> Depending on the location i'm in, 'kt:org-default-publishing-dir' would
> be set to either "~/tmp" or "/plinkx:doxydoc:~/public_html". Without the
> patch, the example above does not work as the value of
> :publishing-directory does not get evaluated.
> > Also, please try to send git patch using these conventions:
> > http://orgmode.org/worg/org-contribute.html#sec-5
> > Thanks a lot!
> Thanks for the hint. I've attached a revised version of the patch which
> includes a changelog/commit msg - i hope that works for you.
> Publish: allow dynamic construction of the publish destination.
> * org-publish.el (org-publish-file): Added 'eval'ing the value of the
> :publishing-directory property before using it as destination of the
> publishing project. This allows to construct the publish destination
> directory dynamically at run-time using the return value of a
> lisp/org-publish.el | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
> index e2213c5..518c1bf 100644
> --- a/lisp/org-publish.el
> +++ b/lisp/org-publish.el
> @@ -684,7 +684,7 @@ See `org-publish-projects'."
> - (or (plist-get project-plist :publishing-directory)
> + (or (eval (plist-get project-plist :publishing-directory))
> (error "Project %s does not have :publishing-directory defined"
> (car project))))))
next prev parent reply other threads:[~2011-10-22 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 18:11 Variable publishing-directory? Kai Tetzlaff
2011-08-18 6:54 ` Bastien
2011-08-18 8:17 ` Kai Tetzlaff
2011-08-18 8:17 ` Variable publishing-directory? (resent with patch as attachment) Kai Tetzlaff
2011-10-22 8:41 ` Bastien Guerry [this message]
2011-10-29 11:55 ` Bastien
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 \
* 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).