#+bind: org-html-preamble

#+bind: org-html-preamble

[Dieter Wilhelm]

Dear list,

for a creating navigation bars (e. g. in duenenhof-wilhelm.de.  I used
to include the respective information e.g. with

#+SETUPFILE: "template_de.org"

and bound in template_de.org org-html-preamble with:

#+BIND: org-html-preamble "<ul id=\"Navigation\"><li><img src=\"img/Aufgescheuchtes-Huhn.png\" width=\"160\" alt=\"image\"/></li><li><a href=\"index.html\">Startseite</a></li><li><hr /></li><li><a href=\"members.html\">Hof und Lebewesen</a></li><li><a href=\"recipies.html\">Rezepte</a></li><li><a href=\"directions.html\">Lage und Anfahrt</a></li><li><a href=\"history.html\">Historie</a></li><li><a href=\"impressum.html\">Impressum / Kontakt</a></li><li><hr /></li><li><a href=\"hewi/index.html\" target=\"_blank\">HeWi Galerie</a></li><li><hr /></li><li><a href=\"dancing/index.html\" target=\"_blank\">Tanzlokalseite</a></li></ul>"

Now in 8.0-pre this mechanism is not working (nothing is included in the
html export files).  Could you please tell me if this is a bug or what I
have missed or - even better - suggest a better/more general way of
including navigation information in html exports.

-- 
Thank you & 
Best wishes

H. Dieter Wilhelm
Darmstadt
Germany

Re: #+bind: org-html-preamble

[Nicolas Goaziou]

Hello,

Dieter Wilhelm <dieter@duenenhof-wilhelm.de> writes:

> for a creating navigation bars (e. g. in duenenhof-wilhelm.de.  I used
> to include the respective information e.g. with
>
>
> #+SETUPFILE: "template_de.org"
>
>
> and bound in template_de.org org-html-preamble with:
>
>
> #+BIND: org-html-preamble "<ul id=\"Navigation\"><li><img src=\"img/Aufgescheuchtes-Huhn.png\" width=\"160\" alt=\"image\"/></li><li><a href=\"index.html\">Startseite</a></li><li><hr /></li><li><a href=\"members.html\">Hof und Lebewesen</a></li><li><a href=\"recipies.html\">Rezepte</a></li><li><a href=\"directions.html\">Lage und Anfahrt</a></li><li><a href=\"history.html\">Historie</a></li><li><a href=\"impressum.html\">Impressum / Kontakt</a></li><li><hr /></li><li><a href=\"hewi/index.html\" target=\"_blank\">HeWi Galerie</a></li><li><hr /></li><li><a href=\"dancing/index.html\" target=\"_blank\">Tanzlokalseite</a></li></ul>"
>
>
> Now in 8.0-pre this mechanism is not working (nothing is included in the
> html export files).  Could you please tell me if this is a bug or what I
> have missed or - even better - suggest a better/more general way of
> including navigation information in html exports.

What is the value of `org-export-allow-bind-keywords'?


Regards,

-- 
Nicolas Goaziou

Re: #+bind: org-html-preamble

[Dieter Wilhelm]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Dieter Wilhelm <dieter@duenenhof-wilhelm.de> writes:

> What is the value of `org-export-allow-bind-keywords'?

org-export-allow-bind-keywords is a variable defined in `ox.el'.
Its value is nil

ahaaaa  there is a new variable! :-)

So this must be set even though

(setq org-export-allow-BIND t)

is already there, or is it replacing this variable?

Thank you for you fast reply!

-- 
Best wishes

H. Dieter Wilhelm
Darmstadt
Germany

Re: #+bind: org-html-preamble

[Nicolas Goaziou]

Dieter Wilhelm <dieter@duenenhof-wilhelm.de> writes:

> org-export-allow-bind-keywords is a variable defined in `ox.el'.
> Its value is nil
>
> ahaaaa  there is a new variable! :-)
>
> So this must be set even though
>
> (setq org-export-allow-BIND t)
>
> is already there, or is it replacing this variable?

It is replacing old `org-export-allow-BIND' (note that they do not share
the same set of possible values).


Regards,

-- 
Nicolas Goaziou

Re: #+bind: org-html-preamble

[Bastien]

Hi Nicolas,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> It is replacing old `org-export-allow-BIND' (note that they do not share
> the same set of possible values).

Is there a reason for not allowing 'confirm?

Also, I'd rather stick to the old name since it is good enough
and will spare many users with the hassle of finding out how to
correctly set the new variable, which is very sensitive.

What do you think?

-- 
 Bastien

Re: #+bind: org-html-preamble

[Nicolas Goaziou]

Hello,

Bastien <bzg@altern.org> writes:

> Hi Nicolas,
>
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> It is replacing old `org-export-allow-BIND' (note that they do not share
>> the same set of possible values).
>
> Is there a reason for not allowing 'confirm?

Yes. It is a pain in the neck to implement, and not vital since you can
specify it as a buffer-local variable anyway.

> Also, I'd rather stick to the old name since it is good enough
> and will spare many users with the hassle of finding out how to
> correctly set the new variable, which is very sensitive.

It isn't sensitive: it defaults to nil. Therefore a user unable to find
it is still safe. Moreover, it will be documented, won't it?

> What do you think?

I didn't like gratuitous caps in the old name. I prefer the new one.
Other than dubious aesthetics reason, I don't mind its name.


Regards,

-- 
Nicolas Goaziou

Re: #+bind: org-html-preamble

[Bastien]

Hi Nicolas,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Bastien <bzg@altern.org> writes:
>
>> Hi Nicolas,
>>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>
>>> It is replacing old `org-export-allow-BIND' (note that they do not share
>>> the same set of possible values).
>>
>> Is there a reason for not allowing 'confirm?
>
> Yes. It is a pain in the neck to implement, and not vital since you can
> specify it as a buffer-local variable anyway.

But it *was* implemented?  If re-using the previous implementation 
is not a pain in the neck, I'd favor re-using it.

>> Also, I'd rather stick to the old name since it is good enough
>> and will spare many users with the hassle of finding out how to
>> correctly set the new variable, which is very sensitive.
>
> It isn't sensitive: it defaults to nil. Therefore a user unable to find
> it is still safe. Moreover, it will be documented, won't it?

See below.

>> What do you think?
>
> I didn't like gratuitous caps in the old name. I prefer the new one.
> Other than dubious aesthetics reason, I don't mind its name.

I'd like to re-use the old name.  I don't like gratuitous caps
in variable names too, but here they directly refer to the normal
appearance of #+BIND.

If we re-introduce the old name, whether it defaults to nil or not
will potentially break users configuration, since a 'confirm value
will either throw an error or (more dangerously) be interpreted as t.

So, if we can re-use the old implementation and the old name, I'm 
for it as it is more flexible.

-- 
 Bastien