emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Fleischer <danflscr@gmail.com>
To: Karl Voit <devnull@Karl-Voit.at>
Cc: emacs-orgmode@gnu.org,  Karl Voit <news2042@Karl-Voit.at>
Subject: Re: Suggested Syntax for cancelled checkboxes: [-] as non-blocking dependency
Date: Wed, 14 Sep 2022 21:18:10 +0300	[thread overview]
Message-ID: <m2h719x1jx.fsf@gmail.com> (raw)
In-Reply-To: <2022-09-13T10-02-59@devnull.Karl-Voit.at> (Karl Voit's message of "Tue, 13 Sep 2022 10:07:53 +0200")

Karl Voit [2022-09-13 Tue 10:07] wrote:

> Is it only me who is thinking that a non-blocking cancelled checkbox
> state would be a good idea?

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. I think it's consistent in terms of
statistics; you want the total number to represent what you wrote down
and what's left does not include the "canceled" tasks. 

-- 
Daniel Fleischer


  parent reply	other threads:[~2022-09-14 18:21 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 [this message]
2022-09-22 15:03       ` Bastien
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=m2h719x1jx.fsf@gmail.com \
    --to=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).