From: Adam Porter <adam@alphapapa.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to organize tasks about Worg within Worg documents
Date: Sun, 31 Mar 2024 10:43:31 -0500 [thread overview]
Message-ID: <ce5ad24f-43cf-458e-868c-eaa808dc7a4a@alphapapa.net> (raw)
In-Reply-To: <87il140zf8.fsf@localhost>
On 3/30/24 05:47, Ihor Radchenko wrote:
> Adam Porter <adam@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.
You make a good point: for some cases, an entire section/heading may
need "to be done," so giving the whole heading a TODO makes sense. For
other tasks, an inline one would be more appropriate.
> 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?
I like the idea of a visual toggle very much, so I'm certainly in favor
of that.
I'm not sure that we must have a constraint on the way TODOs are
written, but having some limitations on or conventions about it might
make such a visual toggle easier to implement (as well as other tools
one might use to collect and visualize tasks across the project).
next prev parent reply other threads:[~2024-03-31 15:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 14:35 [Worg] CSS improvements Adam Porter
2024-03-23 14:49 ` Ihor Radchenko
2024-03-24 6:14 ` Adam Porter
2024-03-24 8:56 ` Ihor Radchenko
2024-03-24 9:28 ` Dr. Arne Babenhauserheide
2024-03-25 14:09 ` Adam Porter
2024-03-26 14:48 ` Ihor Radchenko
2024-03-27 3:20 ` Adam Porter
2024-03-28 11:44 ` Ihor Radchenko
2024-03-28 12:41 ` Adam Porter
2024-03-28 13:18 ` Ihor Radchenko
2024-03-28 17:53 ` Adam Porter
2024-03-29 9:48 ` Ihor Radchenko
2024-03-29 22:38 ` How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements) Adam Porter
2024-03-29 23:30 ` Thomas S. Dye
2024-03-30 2:27 ` How to organize tasks about Worg within Worg documents Adam Porter
2024-03-30 10:47 ` How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements) Ihor Radchenko
2024-03-31 15:43 ` Adam Porter [this message]
2024-04-01 11:34 ` How to organize tasks about Worg within Worg documents Ihor Radchenko
2024-04-01 18:02 ` Adam Porter
2024-03-26 22:12 ` [Worg] CSS improvements David Rogers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce5ad24f-43cf-458e-868c-eaa808dc7a4a@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).