From: Bill Jackson <bill@jacksonhost.com>
To: Jeff Horn <jrhorn424@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Version 7.5: org-export-html-preamble no longer supports function
Date: Tue, 08 Mar 2011 19:48:17 -0800 [thread overview]
Message-ID: <4D76F881.6060507@jacksonhost.com> (raw)
In-Reply-To: <AANLkTinY85_tnq4-bk-gisS=gcS64iVwP431iFyyBsst@mail.gmail.com>
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 source file. Am I missing something?
Jeff Horn wrote, On 3/8/2011 7:35 PM:
> See http://article.gmane.org/gmane.emacs.orgmode/37360/match=preamble
>
> On Tue, Mar 8, 2011 at 9:12 PM, Bill Jackson<wj2@jacksonhost.com> 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 be supported in 7.5.
>>
>> I used this functionality when publishing to generate a preamble and
>> postamble to integrate the generated pages into my website, which included a
>> common page layout, header bar, and footer. I was able to define options in
>> org-export-inbuffer-options-extra, define values for these options in a .org
>> file, and incorporate them into the preamble via the option plist passed to
>> the org-export-html-preamble function.
>>
>> Is there another way in version 7.5 that I can generate custom preambles and
>> postambles incorporating variables from each file at the time of publishing?
>>
>>
>> With much thanks,
>> Bill
>>
>>
>
>
next prev parent reply other threads:[~2011-03-09 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 2:12 Version 7.5: org-export-html-preamble no longer supports function Bill Jackson
2011-03-09 3:35 ` Jeff Horn
2011-03-09 3:48 ` Bill Jackson [this message]
2011-03-09 16:19 ` Bastien
2011-03-09 18:53 ` Bill Jackson
2011-03-10 9:37 ` Bastien
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=4D76F881.6060507@jacksonhost.com \
--to=bill@jacksonhost.com \
--cc=emacs-orgmode@gnu.org \
--cc=jrhorn424@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).