Sébastien Gendre <s...@k-7.ch> writes: > I was modifying the ox-html options alist to add an OPTION key to > `:html-extension'. I do it like this: > > (:html-extension nil "html-extension" org-html-extension) > > But after re-evaluate the ox-html backend definition and adding this to > my org-mode file: > > #+OPTIONS: html-extension:"bear" > > The exported file still have an ".html" extension, and not a ".bear". > > If I debug the function `org-html-export-to-html', its variable `ext-plist' > is empty > and so the function don't use the value of option `:html-extension' but > of variable `org-html-extension' instead. > > Ideally, `org-html-export-to-html' should use the value set with > `#+OPTIONS:' to define the extension of the exported file.
Confirmed. But not easy to fix. This is similar case to https://list.orgmode.org/orgmode/87k05i25lq.fsf@localhost/ At the point when `org-html-export-to-html' is invoked, the buffer keywords are not yet parsed, and we cannot know the contents of the INFO plist. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
