From: Bastien <firstname.lastname@example.org>
Subject: Re: Variable publishing-directory? (resent with patch as attachment)
Date: Sat, 29 Oct 2011 13:55:44 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Kai Tetzlaff's message of "Thu, 18 Aug 2011 10:17:56 +0200")
Kai Tetzlaff <email@example.com> writes:
> 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:
>> 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.
Thanks for the detailed explanations -- for the record,
this patch has been applied a while ago.
prev parent reply other threads:[~2011-10-29 11:54 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 ` [Accepted] " Bastien Guerry
2011-10-29 11:55 ` Bastien [this message]
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).