From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: FR: multiple or repeating active timestamps in agenda Date: Thu, 24 Jan 2008 14:49:56 +0100 Message-ID: <574E0D90-7DEF-4B57-BB5A-97E175761D1D@science.uva.nl> References: <8B89789B-9D8B-4EEF-B81A-35D973EB3FA1@science.uva.nl> Mime-Version: 1.0 (Apple Message framework v915) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JI2Sz-0006Um-Kc for emacs-orgmode@gnu.org; Thu, 24 Jan 2008 08:50:05 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JI2Sw-0006TY-Vr for emacs-orgmode@gnu.org; Thu, 24 Jan 2008 08:50:05 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JI2Sw-0006TV-OV for emacs-orgmode@gnu.org; Thu, 24 Jan 2008 08:50:02 -0500 Received: from ug-out-1314.google.com ([66.249.92.174]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JI2Sw-00033g-GC for emacs-orgmode@gnu.org; Thu, 24 Jan 2008 08:50:02 -0500 Received: by ug-out-1314.google.com with SMTP id a2so307470ugf.48 for ; Thu, 24 Jan 2008 05:50:00 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Austin Frank Cc: emacs-orgmode@gnu.org 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