`:html-preamble` and `:html-postamble` options are lame

`:html-preamble` and `:html-postamble` options are lame

[Luca Sabbatini]

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1006 bytes --]

Re: `:html-preamble` and `:html-postamble` options are lame

[Nicolas Goaziou]

Hello,

Luca Sabbatini <sabbatini.luca@gmail.com> 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