Nicolas Goaziou 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
Nicolas Goaziou writes:
>> For example:
>>
>> - Key: C-c C-w (forge-browse-TYPE) ::
>> + Key: C-c C-w (forge-browse-dwim) ::
>> + Key: N b I (forge-browse-issues) ::
>> + Key: N b P (forge-browse-pullreqs) ::
>> + Key: N b t (forge-browse-topic) ::
>> + Key: N b i (forge-browse-issue) ::
>> + Key
Hello,
Jonas Bernoulli writes:
> I vaguely remember having run into this feature before when using Org to
> record a pros and cons list. As a maintainer I don't like this question
> but; could this feature be made optional? (Of course one could use tags
> to indicate whether an item is a pro o
Nicolas Goaziou writes:
> Hello,
>
> Thanks. Some comments follow.
Thanks for the review!
> Jonas Bernoulli writes:
>
>> +In description lists the used bullet is significant when exporting to
>> +Texinfo; when in doubt, then use =-=. An item that uses =+= instead
>> +becomes a new entry in th
Hello,
Thanks. Some comments follow.
Jonas Bernoulli writes:
> +In description lists the used bullet is significant when exporting to
> +Texinfo; when in doubt, then use =-=. An item that uses =+= instead
> +becomes a new entry in the first column of the table. The above
> +output can also be
* doc/org-manual.org (Plain lists in Texinfo export): Reorder and
document new functionality.
* lisp/ox-texinfo.el (org-texinfo--filter-parse-tree)
(org-texinfo--normalize-items): New functions.
* lisp/ox-texinfo.el (org-texinfo-item): Use @itemx or @item
depending on the used bullet.
---
doc/org-