Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > I suggest to require a special attribute before doing so, e.g., > > #+attr_texinfo: :compact t > - key: a :: > - key: b :: > > - key: c :: > - key: d ::
I have noticed that I accidentally called it ":combine" in the documentation and have fixed that. (Do you think we should stick to ":compact"?) I would actually prefer to be able to set this once per file, not least because this looks a bit weird. #+attr_texinfo: :compact t - key: a :: not "compact" - key: c :: - key: d :: "compact" > Another option would be to merge consecutive lists with such an > attribute, for the same result: > > #+attr_texinfo: :compact t > - key: a :: > - key: b :: > > #+attr_texinfo: :compact t > - key: c :: > - key: d :: That would seem like a fix for that issue, but as I mentioned before that doesn't work because it results in two lists, each with one @item and one @itemx. You actually suggested that in your first reply: >> #+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 become, for example: > > #+options: texinfo+:t > > Could it be possible to use that syntax instead? You later indicated that you would prefer to specify this per-list. I implemented the approach that uses "+" to indicate @itemx items, because that seemed even nicer to me (because more explicit) but you didn't like that and so I went with the alternative that you suggested in response to that attempt. But I would like to take a step back and ask if > #+options: texinfo+:t still seems like a good idea to you. (If so, should that be used instead of the per-list approach or as an alternative?) Jonas