emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Manuel Hermenegildo <herme@fi.upm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: done-ing a repeating scheduled task now inserts closed timestamp?
Date: Wed, 4 Mar 2009 14:30:58 +0100	[thread overview]
Message-ID: <40B5BA0B-49E1-471B-B6B1-9A20BD593AAB@uva.nl> (raw)
In-Reply-To: <9062-Tue03Mar2009095608+0100-herme@clip.dia.fi.upm.es>

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:
> ** 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]
>   - State "DONE"       from "TODO"       [2009-03-03 Tue 07:57]
> An then, with "l" this entry will appear in the agenda, but:
> - 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.
> 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.

Another idea to get this:

Turn on state change notes or at least time stamps.  Either globally,
or locally for this entry with a LOGGING property:

** TODO Check backups
     SCHEDULED: <2009-03-05 Thu 11:00 +2d>

(yes, scheduled, thanks Bernt...)
Then each time you go through the DONE state, a time stamp
will be recorded like this (I am assuming that you have
org-log-into-drawer set...)

** TODO Check backups
    SCHEDULED: <2009-04-28 Tue 11:00 +2d>
    - State "DONE"       from "TODO"       [2009-03-04 Wed 14:25]
    - State "DONE"       from "TODO"       [2009-03-02 Mon 14:25]
    - State "DONE"       from "TODO"       [2009-02-28 Sat 14:25]
    - State "DONE"       from "TODO"       [2009-02-26 Thu 14:25]
    :LOGGING:  DONE(!)

In the agenda, if you press `C-u l', these state notes
will become visible.

I believe this will take care of it, right??

- Carsten

> Thoughts?
> Manuel
> -- 
> -------------------------------------------------------------------------------
> Manuel Hermenegildo                     | Prof., C.S.Dept., T.U.  
> Madrid (UPM)
> Director, IMDEA-Software and CLIP Group | +34-91-336-7435 (W)  
> -352-4819 (Fax)
> -------------------------------------------------------------------------------
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  parent reply	other threads:[~2009-03-04 13:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  1:29 Samuel Wales
2009-03-03  8:56 ` Manuel Hermenegildo
2009-03-04 13:03   ` Carsten Dominik
2009-03-04 14:26     ` Bernt Hansen
2009-03-06 16:49       ` Carsten Dominik
2009-03-07 21:26         ` Bernt Hansen
2009-03-08 18:25         ` Manuel Hermenegildo
2009-03-09  7:41           ` Carsten Dominik
     [not found]             ` <18870.13851.387945.968246@clip.dia.fi.upm.es>
2009-03-11 14:15               ` Carsten Dominik
2009-03-04 13:15   ` Bernt Hansen
2009-03-04 13:30   ` Carsten Dominik [this message]
2009-03-04  6:17 ` Carsten Dominik

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:

  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=40B5BA0B-49E1-471B-B6B1-9A20BD593AAB@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=herme@fi.upm.es \


* 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


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).