From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: done-ing a repeating scheduled task now inserts closed timestamp? Date: Wed, 4 Mar 2009 14:03:21 +0100 Message-ID: <1DF4862F-AD7B-4219-80EF-15483A28EE5E@uva.nl> References: <20524da70903021729g43632321u711b26a43f5b26bf@mail.gmail.com> <9062-Tue03Mar2009095608+0100-herme@clip.dia.fi.upm.es> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Leqky-0006uH-Mo for emacs-orgmode@gnu.org; Wed, 04 Mar 2009 08:03:28 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Leqkx-0006rq-3i for emacs-orgmode@gnu.org; Wed, 04 Mar 2009 08:03:28 -0500 Received: from [199.232.76.173] (port=49974 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Leqkw-0006rh-WA for emacs-orgmode@gnu.org; Wed, 04 Mar 2009 08:03:27 -0500 Received: from mail-ew0-f179.google.com ([209.85.219.179]:63686) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Leqkv-0001xw-4g for emacs-orgmode@gnu.org; Wed, 04 Mar 2009 08:03:26 -0500 Received: by ewy27 with SMTP id 27so2831895ewy.42 for ; Wed, 04 Mar 2009 05:03:24 -0800 (PST) In-Reply-To: <9062-Tue03Mar2009095608+0100-herme@clip.dia.fi.upm.es> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Manuel Hermenegildo Cc: emacs-orgmode@gnu.org On Mar 3, 2009, at 9:56 AM, Manuel Hermenegildo wrote: > >> Nobody else has commented on this, so perhaps I am doing something >> wrong. >> >> My recollection is that [setting the todo state of a task with a >> repeating scheduled task to done] did not used to insert a closed >> timestamp, but now it seems to -- or at least it fails to remove the >> timestamp. Is this intentional? >> >> I use the closed timestamp to indicate that a task can be archived, >> but perhaps I should not rely on that? > > I find that most things in org behave in a way that works for me right > away, which shows how much thinking goes into its design. However > repeated tasks is one thing that has not quite worked for me > yet. Repeating items and cyclic diary entries provide part of the > functionality I need, but not quite. > > Basically, I would like repeated tasks and cyclic appointments to > disappear from the past when they are done (so that they do not > clutter the agenda) but to appear in the future (so that I can, e.g., > schedule other appointments around them in the days they occur). > > Repeating tasks do not appear in the future or the past. Cyclic > appointments are close. If I have: They do appear in the future if you have org-agenda-repeating-timestamp-show-all set to t (which is also the default) > ** TODO Check backups <2009-03-05 Thu 11:00 +2d> > > And pass from TODO to DONE this happens: > > ** TODO Check backups <2009-03-07 Sat 11:00 +2d> > CLOSED: [2009-03-05 Tue 07:57] That CLOSED show up here is a bug, reported by Samuel Wales, fixed by now. > > - State "DONE" from "TODO" [2009-03-03 Tue 07:57] > > An then, with "l" this entry will appear in the agenda, but: Part of the bug that it shows up with "l", it should not. No longer does, I think. > > > - It appears as TODO (rather than DONE) and with the current date, > (even though it also does say "Closed:") all of which can be > confusing. > > - Non-repeating tasks with a timestamp behave differently: if such a > task is marked as done a CLOSED line is also generated (provided the > right flags are on) but it does not actually disappear from the > agenda (at least for me, even if the manual seems to imply > otherwise), independently of the logging ("l") state. You can make DONE scheduled tasks disappear by setting org-agenda-skip-scheduled-if-done Where does the manual state otherwise? > > > I think a perhaps better behavior could be that the same line: > > ** TODO Check backups <2009-03-05 Thu 11:00 +2d> > > is marked as done, then a) a *copy* is made of the TODO item, and that > copy is the one that goes to DONE and gets the CLOSED (i.e., a > "normal" task is generated and updated) and b) the repeating task is > shifted (without attaching anything to it, since it is a "fresh" > task): > > ** DONE Check backups <2009-03-05 Sat 11:00> > CLOSED: [2009-03-05 Tue 07:57] > - State "DONE" from "TODO" [2009-03-03 Tue 07:57] > ** TODO Check backups <2009-03-07 Sat 11:00 +2d> > > Apart from behaving more like a normal task this would have in my mind > some additional advantages: I like DONE tasks to eventually disappear > from my agenda. I do this by archiving them (to sibling). This allows > me to easily see that I have not left anything behind in past days. I > could now do this with the copied task, independently of the updated > repeater. When I want to look at what I did on a certain day I hit the > handy "v" key and the archived, done tasks appear again, including > those that originated from the repeater --great! I.e., the > repeater leaves behind a trail of normal tasks. This is an interesting, alternative proposal for repeating tasks. Anyone else would like to comment on this? - Carsten