From: Ihor Radchenko <yantar92@posteo.net>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements)
Date: Sat, 30 Mar 2024 10:47:07 +0000 [thread overview]
Message-ID: <87il140zf8.fsf@localhost> (raw)
In-Reply-To: <040d14ef-13c2-4955-a059-91f29b29008e@alphapapa.net>
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.
> 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 <adam@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>
next prev parent reply other threads:[~2024-03-30 10:48 UTC|newest]
Thread overview: 23+ 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 ` Ihor Radchenko [this message]
2024-03-31 15:43 ` Adam Porter
2024-04-01 11:34 ` Ihor Radchenko
2024-04-01 18:02 ` Adam Porter
2024-05-12 12:18 ` Ihor Radchenko
2024-05-12 13:42 ` 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=87il140zf8.fsf@localhost \
--to=yantar92@posteo.net \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
/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).