emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Manuel Hermenegildo <herme@fi.upm.es>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: Bernt Hansen <bernt@norang.ca>, emacs-orgmode@gnu.org
Subject: Re: done-ing a repeating scheduled task now inserts closed timestamp?
Date: Sun, 8 Mar 2009 19:25:28 +0100	[thread overview]
Message-ID: <18868.3480.497640.673958@clip.dia.fi.upm.es> (raw)
In-Reply-To: <E4F889D6-E90D-4D99-AE7F-FDA1649146F7@uva.nl>

Sorry for the pause (I was pretty busy last week):

 > 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>
 >     :LOGGING: DONE(!)
 >     :END:
 > (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>
 >     :LOGBOOK:
 >     - 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]
 >     :END:
 >     :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??

Yes, this is much closer than what one would like.  And having those
"done states" together could be useful. 

However, I have to say that though that after trying to adapt to these
settings I cannot bend my mind to find the behavior comfortable,
specially comparing to how normal tasks work. 

For me it is confusing that when I do "t" on such a task it goes to
"DONE" as I would expect (i.e., like a normal TODO task) but when I
refresh the agenda it disappears (unlike normal DONE tasks, at least
with my settings --I use archiving to make done tasks disappear and
"v" to toggle viewing archived tasks).  Actually, I think it goes to
DONE only for the first repeat, for the following repeats it stays as
TODO, at least with my settings.  

I guess I can use org-agenda-skip-scheduled-if-done to get the
non-repeating tasks to disappear also when marked as done (so that
there is more orthogonality) but, again, it will only work if I
remember to use "SCHEDULED" for them, and, also, I do not want them to
disappear yet! ;-)

Also, I feel I have to remember too many things for, say, a simple
weekly meeting: a) putting SCHEDULED, b) setting the properties, c)
making sure org-log-into-drawer is set, etc.  Ideally any simple TODO
entry with a repeating timestamp should behave well when marked as
done, right?

 > to me this sounds like a pretty convincing argument *not*
 > to copy entries...

Yes, I guess this is a problem (although in my case all repeating
entries --which are regular meetings, classes, birthdays, etc.-- are
typically one liners so it would not make a difference if they were

Sorry to insist, but I still think copying the tasks would produce a
more orthogonal behavior. Perhaps it could be made optional?


 Manuel Hermenegildo                     | Prof., C.S.Dept., T.U. Madrid (UPM)
 Director, IMDEA-Software and CLIP Group | +34-91-336-7435 (W) -352-4819 (Fax)

  parent reply	other threads:[~2009-03-09  7:06 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 [this message]
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
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=18868.3480.497640.673958@clip.dia.fi.upm.es \
    --to=herme@fi.upm.es \
    --cc=bernt@norang.ca \
    --cc=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \


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