From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dennis J Lin Subject: Re: Re: BUG?: repeat items disappears in agenda Date: Sun, 20 Jan 2008 11:21:07 -0600 Message-ID: <20080120172107.GK17250@seeker.homedns.org> References: <4790CE1B.8040701@gmail.com> <874pdaomid.fsf@uiuc.edu> <7B164E1D-3884-4BBF-AB2B-E90068254CEF@science.uva.nl> <20080118215529.GG17250@seeker.homedns.org> <48F709E7-8D83-4021-8AA1-4AB71A9ECE53@science.uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JGdry-0005SK-Nj for emacs-orgmode@gnu.org; Sun, 20 Jan 2008 12:22:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JGdrw-0005Qg-Rw for emacs-orgmode@gnu.org; Sun, 20 Jan 2008 12:22:06 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JGdrw-0005QX-Gl for emacs-orgmode@gnu.org; Sun, 20 Jan 2008 12:22:04 -0500 Received: from jadzia.ifp.uiuc.edu ([130.126.122.22]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JGdrv-0001Yf-MB for emacs-orgmode@gnu.org; Sun, 20 Jan 2008 12:22:04 -0500 Content-Disposition: inline In-Reply-To: <48F709E7-8D83-4021-8AA1-4AB71A9ECE53@science.uva.nl> 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: Carsten Dominik Cc: emacs-orgmode@gnu.org Salutations! > Hi Dennis, thanks for the patch. > > I am not sure yet if you are using the right condition though. It seems to > me that extending the late-warning-period makes sens only for repeating > *tasks*, where the base date keeps changing each time you mark this entry > as DONE. So maybe the condition should be that it is today *and* that the > item is a task marked by a TODO keyword. Hmm, that may be -- every entry that has a date is a TODO for me. I would think that a non-todo entry (repeating or not) should only occur on the day(s) where it's scheduled, since there is no way to mark it "done" and get it off of today's agenda. > Or: maybe for Scheduled, we should no relate to the *nearest* match of the > repeater, but to the most recent one. This way you would get over-due > warnings right up to the day where the next occurrence of this item is > scheduled. So you would never loose sight on the item. However, if we do this, we lose information on *how* overdue a particular item is. I tend to keep things on the agenda and let the large numbers shame me into getting things done... Dennis Lin