From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Jackson Subject: Function for html-preamble and html-postamble in org-publish Date: Sun, 11 Dec 2011 15:38:13 -0800 Message-ID: <4EE53EE5.7040103@jacksonhost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:46607) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RZsyA-0002P8-Rp for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 18:38:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RZsy9-0005EJ-Te for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 18:38:10 -0500 Received: from oproxy5-pub.bluehost.com ([67.222.38.55]:34683) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RZsy9-0005E9-KD for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 18:38:09 -0500 Received: from ip68-4-162-105.oc.oc.cox.net ([68.4.162.105] helo=[192.168.1.107]) by box291.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1RZsy7-00079K-5E for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 16:38:07 -0700 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org In version 7.7, a function provided to org-publish via :html-preamble or :html-postamble no longer accepts a property list of export options. I do not know if this change is a bug, or if it is deliberate. I pass functions to :html-preamble and :html-postamble to integrate generated HTML pages into a web site. In previous versions of org-mode, such functions took a single argument as documented in org-export-html-premable: "The function takes the property list of export options as its only argument." In version 7.7 this appears to have changed in org-html.el, org-export-as-html, lines 1,340 and 1,791 (they no longer pass opt-plist), without any change to documentation. Further changes to this code have been made in the git repository. I was able to restore the previous behavior simply by editing org-html.el to again pass opt-plist on the two lines, but am interested in what the future direction is for customizing the HTML output for org-publish. Was this change unintentional, a deliberate minor change, or is org-publish or org-html undergoing significant re-design? If this was deliberate, is there an alternate method for customization functions to access the property list? Thanks for any insight, Bill