This looks great to me. Seems like a relatively "more sane" or perhaps
"more intuitive" way of doing things. Solves the problem I had
earlier, and makes it clear that these variables can be set in an init
file.
On Thu, Feb 10, 2011 at 11:25 AM, Manuel Giraud
wrote:
> Bastien writes:
>
>> As for
Bastien writes:
> Would people welcome such a simplification?
I've tried it and find it better (and simpler) then with
:auto-preamble/:preamble.
Some comments:
+ example in info file is not the same as before because postamble
is on by default (maybe we could put a formated string
Manuel Giraud writes:
> Bastien writes:
>
>> As for org-export-html-preamble and -postamble being t by default, it's
>> a mistake I made. I think they should default to nil. But I'd welcome
>> another opinion!
>
> For the postamble maybe. But for the preamble, I don't think it is a
> good id
Bastien writes:
> As for org-export-html-preamble and -postamble being t by default, it's
> a mistake I made. I think they should default to nil. But I'd welcome
> another opinion!
For the postamble maybe. But for the preamble, I don't think it is a
good idea to remove the title by default
Manuel Giraud writes:
> Bastien writes:
>
>> Would people welcome such a simplification?
>
> I've tried it and find it better (and simpler) then with
> :auto-preamble/:preamble.
Thanks for the feedback!
> Some comments:
>
> + example in info file is not the same as before because postambl
Here is a patch against latest git Org that tries to simplify the
handling of HTML preamble/postamble: I find the interaction between
:preamble and :auto-preamble a bit confusing and a recent questions by
Jeff on customizing org-export-html-preamble raised this issue.
So here is what I suggest:
-
