From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: `:html-preamble` and `:html-postamble` options are lame Date: Fri, 29 Mar 2013 22:08:37 +0100 Message-ID: <87ehexx6ay.fsf@gmail.com> References: <5155EFAC.1050208@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:42879) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULgXV-0004hT-Pz for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 17:08:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ULgXU-0003gN-Vf for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 17:08:45 -0400 Received: from mail-wi0-x230.google.com ([2a00:1450:400c:c05::230]:48676) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULgXU-0003g8-PT for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 17:08:44 -0400 Received: by mail-wi0-f176.google.com with SMTP id hm14so203878wib.15 for ; Fri, 29 Mar 2013 14:08:43 -0700 (PDT) In-Reply-To: <5155EFAC.1050208@gmail.com> (Luca Sabbatini's message of "Fri, 29 Mar 2013 14:46:52 -0500") 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: Luca Sabbatini Cc: emacs-orgmode@gnu.org Hello, Luca Sabbatini writes: > 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? Could you provide the Org version you're using, and an ECM reproducing the problem? Regards, -- Nicolas Goaziou