Adam Porter <a...@alphapapa.net> writes: > Using a normal heading for a task would "commandeer" the structure of > the document, which I think is a real problem.
Not really. If some section is incomplete, marking it "TODO" means that it should be completed. And the details might be listed in the logbook notes, for example. The section name itself does not necessarily have to details what needs to be done. We have multiple instances of such "TODO" items in WORG, some also include comments on what should be done. On the other hand, inlinetasks are more concrete and immediately mark both where exactly and what needs to be done. > ISTM that there are a few potential solutions: > > a. Using inline tasks... > > b. Using commented lines... > > c. Keeping tasks in a separate file... > ... "Thomas S. Dye" <tsd@tsdye.online> writes: > d. Keeping tasks under a heading held back from export... > ... Adam Porter <a...@alphapapa.net> writes: > Regardless of the decision, I do think that having this stated as a > policy somewhere would be helpful. > > WDYT? I am not 100% sure if we need to constrain "TODO" items to one or another style. Global todo list, marking existing sections as TODO, and inlinetasks all may have their place depending on the situation. The policy we may want to set is whether "TODO" keywords and notes should be displayed to all the users. WORG has this set all over the place - some TODO headings are marked to be not exported, some TODO keywords are hidden via #+options: todo:nil, some notes are placed into # comments. May we have some kind of css-based toggle that will enable "developer mode", revealing all the todo keywords, inlinetasks, and notes? Then, we hide the "unfinished" parts from users by default, but let them see what can be contributed? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
