Hi Gregor, thanks for the detailed report.
Gregor Zattler <telegr...@gmx.net> writes: > Summary: > > 1) With respect to visibility cycling I would expect to see > inline tasks as normal text or plainlist item. I would not > expect the display of children or subtrees to be cut of > immediately after an inline task. > > This is my main concern. (Hierarchical) plain lists are so > useful. Tasks are useful. One workaround to combine the > two would be to use headings instead of plain lists. But this > looks terrible even with the `hidestars' option and and > especially in all kinds of exports. > > 2) I would not expect to see an error when doing org-cycle with > certain variable settings. If org-mode is not able to handle > this situation it should tell so in a way the user is able to > act upon. It might disappoint you, but by take on this is very simple: you should not try to use inline tasks within plain lists. I added this note in the comment header of org-inlinetask.el: ;; Note that you should not try to use inline tasks within plain list, ;; visibility cycling is known to be problematic when doing so. If anyone is willing to support inline tasks within plain list, please send a patch. Thanks, -- Bastien
