Hi Ruben,
Thanks for your patch.
Ruben Maher <r...@rkm.id.au> writes:
> I've been working on a derived exporter to publish a static blog, and
> I've run into some issues. Say that `:publishing-directory' is
> "~/public_html" and I have `:base-directory' with an Org file foo.org.
>
> foo.org has option keywords like this:
>
> #+title: foo.org
> #+date: <2015-07-25 Sat 17:21:41>
OK. That's nice.
> I have achieved this using the attached diff, which tells
> `org-export-output-file-name' to respect the property `:output-file' in
> the communications channel.
OK. I did not test your patch, but can you please test and indicate
whether the following features work as expected with your patch:
- automatic sitemap.
- linking org files (foo.org links to bar.org).
- async export (since you change org-export-output-file-name)
Some quick thoughts. Perhaps it would be better to allow either a
user-supplied function that takes an org parse tree or an org file
location and returns an output name. Alternatively, maybe you could
provide a way to format file names in :publish-direction via a
format-string (e.g. keywords, date etc).
> From 13c92b87b728da134a73ef173be8957453ef90a6 Mon Sep 17 00:00:00 2001
> From: Ruben Maher <r...@rkm.id.au>
> Date: Sat, 25 Jul 2015 16:54:28 +0930
> Subject: [PATCH] org-export-output-file-name: respect :output-file
>
> There is a property :output-file defined in the communications channel
> but it is ignored by `org-export-output-file-name'.
>
> * lisp/ox.el (org-export-output-file-name): Add optional argument
> EXT-PLIST, and try to get `base-name' from its property `:output-file'
> if SUBTREEP is nil or there was no EXPORT_FILE_NAME at point.
Nicolas would have to say whether this is OK. I don't know the details
here well enough.
Rasmus
--
May the Force be with you
