Arun Isaac writes:
> After 5cd793c, the documentation for the preparation function says
> "Each preparation function is called with a single argument, the project
> property". This could be clearer if it is "... the project property
> list", as it is in the documentation for the completion functi
> Done in 5cd793c.
After 5cd793c, the documentation for the preparation function says
"Each preparation function is called with a single argument, the project
property". This could be clearer if it is "... the project property
list", as it is in the documentation for the completion function.
si
Hello,
Arun Isaac writes:
>> 2. Require preparation functions to accept one parameter, the project
>>plist.
>
> I think adding project-plist as a parameter to preparation functions is
> definitely more elegant.
Done in 5cd793c.
> But, I also came across this old thread where it was noted t
> 2. Require preparation functions to accept one parameter, the project
>plist.
I think adding project-plist as a parameter to preparation functions is
definitely more elegant.
But, I also came across this old thread where it was noted that making
project-plist a proper parameter, instead of
Hello,
Arun Isaac writes:
> The org mode manual says "The project property list is scoped into this
> call as the variable project-plist". But, ox-publish.el has lexical
> binding enabled, and the variable project-plist doesn't seem to be
> accessible from the executed preparation-function. When
The org mode manual says "The project property list is scoped into this
call as the variable project-plist". But, ox-publish.el has lexical
binding enabled, and the variable project-plist doesn't seem to be
accessible from the executed preparation-function. When I try to access
the variable, I get
