Sorry for the delay, I got side-tracked with many other things.
Nicolas Goaziou writes:
>>> It is possible to mix the two styles;
>>
>> Well... it turned out not to be true, but I should be able to get it
>> to work.
>
> Then I suggest to use "attr_texinfo" keyword, for example:
>
>#+attr_te
Hello,
Jonas Bernoulli writes:
> Of course. I probably used the separate keyword because all the entries
> for ox-texinfo's :options-alist did that too, but if that's not how this
> is usually done for booleans, then I see no reason not to change it.
More precisely, there's an historical disti
Nicolas Goaziou writes:
> I like the idea, thank you for suggesting it.
Great :D
>>#+TEXINFO_DEFFN: t
>
> The chosen UI is rather odd however. I cannot think of another use of
> controlling export thhough "#+keyword: boolean" syntax. Usually, we
> extend the "options" keyword. It could becom
Hello,
Jonas Bernoulli writes:
> I recently talked to Bastien about this and he encouraged to bring up
> the possibility of merging ox-texinfo+.el into ox-texinfo.el.
>
> ox-texinfo+ (https://github.com/tarsius/ox-texinfo-plus) has several
> features but the one I would like to talk about now is
Hello,
In the olden days before Org's own manual was written using an org-mode
file, I started doing just that for Magit. Because ox-texinfo.el wasn't
quite there yet I wrote an extension, ox-texinfo+.el, to fill in the
gaps. Since then I have written seven more manuals that use my
extension.
I
