From: Bastien <bzg@gnu.org>
To: Daniel Fleischer <danflscr@gmail.com>
Cc: Karl Voit <devnull@Karl-Voit.at>,
emacs-orgmode@gnu.org, Karl Voit <news2042@Karl-Voit.at>
Subject: Re: Suggested Syntax for cancelled checkboxes: [-] as non-blocking dependency
Date: Thu, 22 Sep 2022 17:03:17 +0200 [thread overview]
Message-ID: <87bkr7ih8q.fsf@gnu.org> (raw)
In-Reply-To: <m2h719x1jx.fsf@gmail.com> (Daniel Fleischer's message of "Wed, 14 Sep 2022 21:18:10 +0300")
Daniel Fleischer <danflscr@gmail.com> writes:
> At first it makes sense, but we do have headlines and TODO keywords to
> express different states, colors and even sets of states. This is just a
> checklist construct. I think if I wanted to mark something as canceled
> or not relevant I would do something like this:
>
> - [ ] this is important.
> - [X] +canceled+ this is not important.
>
> or even strike through everything.
FWIW, I use this:
- [X] +This task will probably be canceled+
I don't think we should implement a new status for canceled tasks.
On top of the implementation (C-u C-u C-u C-c C-c ?), I believe it
is more flexible to be able to let canceled tasks block the whole
set of tasks---or not. So both these tasks seem useful to me:
- [X] +A canceled task+
- [-] +A canceled task+
Implementing "canceled tasks" will probably force one interpretation
over another, we lose in flexibility and readability.
2 cts,
--
Bastien
next prev parent reply other threads:[~2022-09-22 15:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 12:40 Suggested Syntax for cancelled checkboxes: [-] as non-blocking dependency Karl Voit
2022-09-13 2:24 ` Ihor Radchenko
2022-09-13 8:07 ` Karl Voit
2022-09-13 10:44 ` Marcin Borkowski
2022-09-13 11:07 ` Christophe Schockaert
2022-09-13 15:52 ` Karl Voit
2022-09-14 12:43 ` Ihor Radchenko
2022-09-15 11:48 ` Christophe Schockaert
2022-09-16 4:59 ` Ihor Radchenko
2022-09-19 11:10 ` Karl Voit
2022-09-14 18:18 ` Daniel Fleischer
2022-09-22 15:03 ` Bastien [this message]
2022-09-22 17:19 ` Milan Zamazal
2022-09-22 23:19 ` Tim Cross
2022-09-23 2:46 ` Ihor Radchenko
2022-09-25 2:59 ` Bastien
2022-09-24 8:09 ` Milan Zamazal
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=87bkr7ih8q.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=danflscr@gmail.com \
--cc=devnull@Karl-Voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news2042@Karl-Voit.at \
/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).