From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Bug: Recurring items NEVER show up in timeline unaccompanied Date: Wed, 23 Mar 2011 14:56:02 -0400 Message-ID: <3351.1300906562@alphaville.usa.hp.com> References: Reply-To: nicholas.dokos@hp.com Return-path: Received: from [140.186.70.92] (port=56445 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q2TDy-0002gH-66 for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 14:56:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q2TDw-0004T2-Pt for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 14:56:06 -0400 Received: from g5t0006.atlanta.hp.com ([15.192.0.43]:23066) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q2TDw-0004Su-KA for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 14:56:04 -0400 In-Reply-To: Message from "Mark S" of "Wed, 23 Mar 2011 10:02:41 -0800." 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: throaway@yahoo.com Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org Mark S wrote: > > Lisp tends to bring out my inner dyslexic, but is it possible to use > a "while" or other construct instead of "mapcar" and then make the > "if" construction inside of the lambda check for the :omitted symbol > and return it as nil? And it would need to break out of the loop as > soon as it encountered a date equal or greater to the present. > > Philosophically, the way I think the calendar should work for > recurring events is that they only occur until the last event in the > calendar UNLESS an argument has been given to specify how far out the > calendar is to be drawn OR there is a global end-date / end-range > variable. > The bug is indeed easy to fix. What's harder is to figure out how things *should* work as you point out: o where should it start? should the timeline include past dates by default? when the user says so? should it *ever* include past dates? o where should it stop? The last explicit entry is one possibility, user-input is another (but this would require changes to the user interface), a time limit specified by the user in some configuration variable is a third. The more one looks at these things, the more one marvels at the choices that Carsten and Bastien and Nicolas and the Babel developers (and on and on) have made: getting things so that they work *just* right most of the time and providing enough flexibility to cover most of the remaining cases is hard work. Nick