Re: [PATCH] Introduce "export features"

[Sébastien Miquel]

Ihor Radchenko writes:
> > > The traditional user-facing approach for toggling staff in export is
> > > setting export options.
> > Indeed. Then I suggest that such use be described in the manual.
> > Having the user create a whole new option in order to toggle a
> > `chikenize` package seems a bit unwieldy, however.
> What do you suggest instead of creating a new option?

Timothy's patch supports having a feature depend on a variable. I was
thinking here of a user variable (instead of an already defined org
variable) that could be toggled per document.

It is fairly orthogonal to the original purpose of the patch, but it
does scratch an annoying itch of mine: there's very little support in
org to minutely tweak the export on a per document basis, beyond the
default options.

One way to do this (easier than setting up a new option), is to define
any variable, make the feature depend on it, and set it using the
`#+bind` keyword. Combined with these export features, this could be
used to easily tweak the LaTeX preamble, per document.

If we find this use case to be legitimate and useful, I suggested
earlier making it even easier with a `#+org_export_features` keyword.
It would only take a list of feature names, and not require any
variable tied to the feature.

--
Sébastien Miquel