Ihor Radchenko <yanta...@gmail.com> writes: > For reference, I am seeing this feature as a step towards better > modularity of org-list.el.
Modularity is good if we have use-cases for it, at least one feature relying on it. I wouldn't implement a feature just to add modularity. > The current list code is rather monolithic > and leaves no room for user customization of the commands. (Also, see > recent discussions about converting between lists and headings > https://list.orgmode.org/orgmode/877d4luxb8.fsf@localhost/ > https://orgmode.org/list/877d3k70lu.fsf@localhost) I'm not convinced the first report is a bug in the way list are handled. The second is a bug in the way headings are transformed as list items (leaving footnotes in a poor state). If more modularity helps fixing these edge cases, then why not. > Even if we do not provide "canceled" items in lists, having an > infrastructure to customize list commands better will be a good thing to > have. Of course, I guess you can think of useful customization of list commands -- perhaps that what we should think about first: would it be a good thing to allow customization of list commands? what use-case? 2 cts, -- Bastien
