Re: FR: multiple or repeating active timestamps in agenda

[Austin Frank <austin.frank@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2652 bytes --]

On Tue, Jan 22 2008, Carsten Dominik wrote:

> Hi Austin,
>>
>> I'd like to be able to mark it as done every week, without needing it
>> to be SCHEDULED or have a DEADLINE.  Currently, the first time I mark
>> it as done, all past and future repetitions are also marked as done.
>
> What is the purpose of marking it done?  It is not going to be on your
> agenda after that day, if you have notes for the meeting you can just
> add them.  So I don't really see the use of this.

The point of marking it done is mostly to have a record of having
completed it.  I'm trying to use org to generate reports of what I get
done each week, and attending recurring meetings and courses is a large
portion of the stuff I have to do.  I'd like a way to include these
recurring events in the list of things I've accomplished.

I could create a new task for each instance of the event, but a) I worry
I would forget, and b) that gets to be a hassle when it's something that
happens two or three times a week over several months.

>> Given that we can't combine repetition intervals with date ranges (or
>> can we?),
>
> No, we cannot.

Understandable, for exactly the reasons you mention below.

>> --8<---------------cut here---------------start------------->8---
>> * Standing Appointments
>> ** Swing III
>> *** TODO Week 1
>>    <2008-01-21 Mon 19:30-21:30>
>> *** TODO Week 2
>>    <2008-01-28 Mon 19:30-21:30>
>> *** TODO Week 3
>>    <2008-02-04 Mon 19:30-21:30>
>> --8<---------------cut here---------------end--------------->8---
>>
>
> I'd say this is a pretty good way of dealing with a limited amount of
> meetings.

I will probably use this structure to deal with this case.  I would
still appreciate any suggestions from the list on how to include
recurring events as TODO items without marking them as SCHEDULED or
DEADLINE.  Has anyone else dealt with this situation?

> Yes, I am lazy to no implement this, but believe me, time stamp
> handling is complex already, in part because I have been adding the
> new features one at a time.  Had I know from the start what kind of
> features would be goot, time ranges with repeater intervals would
> probably be in.  Now, it is hard to do.  I'll put it into my tickler
> file, but no promises....

Org is obviously already incredibly useful.  I'm certainly not
complaining, just looking for the best way to fit org to my thinking and
vice versa.  Thanks for considering the request, and for all of the
features that already are in org.

/au

-- 
Austin Frank
http://aufrank.net
GPG Public Key (D7398C2F): http://aufrank.net/personal.asc

[-- Attachment #1.2: Type: application/pgp-signature, Size: 185 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
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