From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Sabbatini Subject: `:html-preamble` and `:html-postamble` options are lame Date: Fri, 29 Mar 2013 14:46:52 -0500 Message-ID: <5155EFAC.1050208@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------050204040807070704030309" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:44463) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULfGP-0003uR-3H for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 15:47:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ULfGJ-00086w-Ny for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 15:47:01 -0400 Received: from mail-ia0-x231.google.com ([2607:f8b0:4001:c02::231]:48225) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULfGJ-00086m-If for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 15:46:55 -0400 Received: by mail-ia0-f177.google.com with SMTP id w33so638373iag.22 for ; Fri, 29 Mar 2013 12:46:54 -0700 (PDT) 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 This is a multi-part message in MIME format. --------------050204040807070704030309 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit It seems to be that the `:html-preamble` and `:html-postamble` export options are impotent. They are overridden if the `org-export-html-preamble-format` and `org-export-html-postamble-format` are set to *anything*. In order for the `:html-preamble` and `:html-postamble` html export options to even be considered during export, one must set their corresponding format variables to `nil`. But by then there's effectively no preamble or postamble to disable anyway. How is one expected to make use of the :html-preamble` and `:html-postamble` options? (Perhaps I have misunderstood something). In any case, shouldn't the options override the internal variables during export on the per-file basis? Thank you for your time, Luca --------------050204040807070704030309 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit It seems to be that the `:html-preamble` and `:html-postamble` export options are impotent. They are overridden if the `org-export-html-preamble-format` and `org-export-html-postamble-format` are set to *anything*.

In order for the `:html-preamble` and `:html-postamble` html export options to even be considered during export, one must set their corresponding format variables to `nil`. But by then there's effectively no preamble or postamble to disable anyway.

How is one expected to make use of the :html-preamble` and `:html-postamble` options? (Perhaps I have misunderstood something).

In any case, shouldn't the options override the internal variables during export on the per-file basis?

Thank you for your time,

Luca
--------------050204040807070704030309--