emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Recurring TODO spuriously blocked [7.7]
Date: Mon, 12 Dec 2011 19:44:16 -0500	[thread overview]
Message-ID: <87k461l2qn.fsf@norang.ca> (raw)
In-Reply-To: <87wra1sj1e.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Mon, 12 Dec 2011 14:10:21 -0500")

pinard@iro.umontreal.ca (François Pinard) writes:

> Bernt Hansen <bernt@norang.ca> writes:
>
>> pinard@iro.umontreal.ca (François Pinard) writes:
>
>>> todo-dependencies should likely never be enforced for repeated
>>> entries, even if enforced otherwise, as enforcing for repetitions
>>> with the current Org mechanics has no meaning, at least as I
>>> undestand Org so far.
>
>> You can set a NOBLOCKING property to t to skip the dependency check for
>> repeated tasks.
>
>> * TODO Some Repeating Task
>>   SCHEDULED: <2011-12-16 Fri 15:30 ++1w>
>>   :PROPERTY:
>>   :NOBLOCKING: t
>>   :END:
>
> Thanks for the hint, Bernt.  I'll use it for now.
>
> I still think this is a work around a real problem, which would ideally
> be corrected.  Regardless of blocking being configured or not for
> non-repeating tasks, repeated tasks should never be blocked, shouldn't
> they?
>
> François

Hi François,

I think the answer to that question is "it depends".  I think there is a
way to make check boxes block tasks too (but I've never used it) and in
conjunction with resetting all of the checkboxes to unchecked you
probably don't want to do that accidentally half way through your list
of done items.

I think this preference is very much workflow driven and shouldn't be
globally assigned for everyone.  I'm fine with an option that selects
the behaviour globally so you can customize it the way you like.

It would be nice if subtasks (that are DONE) get automatically moved
back to TODO when the parent repeating task is marked DONE (and goes
back to TODO).  It's just not an itch anyone has scratched yet.  If
repeating tasks behaved this way (in the future) I think keeping the
blocking functionality for repeating tasks makes sense.

Regards,
Bernt

  reply	other threads:[~2011-12-13  0:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12  3:34 Bug: Recurring TODO spuriously blocked [7.7] François Pinard
2011-12-12 17:35 ` Bernt Hansen
2011-12-12 19:10   ` François Pinard
2011-12-13  0:44     ` Bernt Hansen [this message]
2011-12-13  1:33       ` François Pinard

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=87k461l2qn.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    /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).