From: Milan Zamazal <pdm@zamazal.org>
To: emacs-orgmode@gnu.org
Subject: Re: Suggested Syntax for cancelled checkboxes: [-] as non-blocking dependency
Date: Thu, 22 Sep 2022 19:19:01 +0200 [thread overview]
Message-ID: <87leqbuy2i.fsf@zamazal.org> (raw)
In-Reply-To: 87bkr7ih8q.fsf@gnu.org
>>>>> "B" == Bastien <bzg@gnu.org> writes:
B> FWIW, I use this:
B> - [X] +This task will probably be canceled+
B> I don't think we should implement a new status for canceled
B> tasks.
Such a workaround doesn’t work well for lists that are to be re-used
next time or cleared when the whole task is repeating and is switched to
done. Checkboxes can always be cleared easily using a single
rectangular command if there is no automatic mechanism but how to clear
the + marks?
A typical example would be my checklist for items to take with when
traveling. Some of the items are already in my bag, some must be
inserted there and some are not needed this time. Using +strike
through+ is cumbersome, defining a command for it doesn’t feel good, and
there is the problem of clearing the marks when re-using the list next
time. Well, I do not store that particular list in a task node so I can
use [-] freely but it’s still inconsistent with the actual meaning
defined by Org. Not that big deal but it would be nice to have an
official way to mark an item as not-applicable / canceled and not
blocking finishing the task.
next prev parent reply other threads:[~2022-09-22 18:58 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
2022-09-22 17:19 ` Milan Zamazal [this message]
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=87leqbuy2i.fsf@zamazal.org \
--to=pdm@zamazal.org \
--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).