[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Orgmode] Re: done-ing a repeating scheduled task now inserts closed tim

From: Carsten Dominik
Subject: [Orgmode] Re: done-ing a repeating scheduled task now inserts closed timestamp?
Date: Mon, 9 Mar 2009 08:41:38 +0100

Hi Manuel,

first of all, you don't need to take notes into the LOGBOOK drawer.
If that is off, notes will be just added after the heading.

Second, setting the properties for logstate or lognotestate
is actually not necessary at all, my mistake.
It is sufficient to have org-log-repeat set, and the default
is `time', so you should automatically get a time stamp each
time an entry repeats.  Don't you?

About the behavior in the agenda, I think it is already
very nice of me :-) to show you the task as DONE until the
next refresh - because in the original buffer, is is actually
already TODO again.

If you always want to see state changes when you press `l' in the
agenda (i.e. by default, without pressing `C-u l'), then you
can configure the variable org-agenda-log-mode-items to include
also the symbol `state'.

For the copying, I think we really need to make a difference
between a single task that repeats, and many similar tasks,
which is what you are talking about.

A single task that repeats is the current behavior, and I still
believe it makes sense this way.

Why, if you want to have many tasks instead of one, don't
you just create many directly, with different dates.  A keyboard
macro would work for this, or a little function that does the
copying and time shifting.

I may make a function that copies a task N times
with a certain date shift.

The more I think about the automatic copying when DONE, the less
sense it makes to me, I am afraid.

- Carsten

On Mar 8, 2009, at 7:25 PM, Manuel Hermenegildo wrote:

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>

(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]

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)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]