From: Carsten Dominik <dominik@science.uva.nl>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: FR: multiple or repeating active timestamps in agenda
Date: Thu, 24 Jan 2008 14:49:56 +0100 [thread overview]
Message-ID: <574E0D90-7DEF-4B57-BB5A-97E175761D1D@science.uva.nl> (raw)
In-Reply-To: <m0abmxgawv.fsf@gmail.com>
On Jan 22, 2008, at 4:03 PM, Austin Frank wrote:
> 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.
I do now think that I can allow repeater appointments to interact
with the TODO state as you proposed. So lets try this in 5.20.
Still no end date for repeating appointments, sorry.
- Carsten
prev parent reply other threads:[~2008-01-24 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 21:20 FR: multiple or repeating active timestamps in agenda Austin Frank
2008-01-22 9:36 ` Carsten Dominik
2008-01-22 15:03 ` Austin Frank
2008-01-22 18:36 ` Detlef Steuer
2008-01-24 13:49 ` Carsten Dominik [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=574E0D90-7DEF-4B57-BB5A-97E175761D1D@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=austin.frank@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).