Hi Bill,
Bill Jackson writes:
> This works for me.
thanks for testing.
> I have not tested it _carefully_, but I did apply your
> patch and my setup now works as it did before. (Of course :preamble and
> :postamble needed to be changed to :html-preamble :html-postamble for
> org-publish.)
Bastien wrote, On 3/9/2011 8:19 AM:
Bill Jackson writes:
In version 7.4, org-export-html-preamble and org-export-html-postamble
could be set to the name of a function that was passed an option plist.
See my last patch. It allows to set org-export-html-pre/postamble to a
function that will re
I had read this discussion thread (more than once!), but have not been
able to figure out how to accomplish what I was doing under 7.4 without
support for passing a function in org-export-html-preamble. I know how
to generate a preamble, but not how to generate one customized for each
.org sou
Hi Bill,
Bill Jackson writes:
> In version 7.4, org-export-html-preamble and org-export-html-postamble
> could be set to the name of a function that was passed an option plist.
See my last patch. It allows to set org-export-html-pre/postamble to a
function that will return a string. The funct
See http://article.gmane.org/gmane.emacs.orgmode/37360/match=preamble
On Tue, Mar 8, 2011 at 9:12 PM, Bill Jackson wrote:
> In version 7.4, org-export-html-preamble and org-export-html-postamble could
> be set to the name of a function that was passed an option plist. This
> appears to no longer
In version 7.4, org-export-html-preamble and org-export-html-postamble
could be set to the name of a function that was passed an option plist.
This appears to no longer be supported in 7.5.
I used this functionality when publishing to generate a preamble and
postamble to integrate the generat
