From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: Re: iCal export of repeated tasks Date: Fri, 13 Jun 2008 12:48:05 +0100 Message-ID: <20080613114805.GC8066@atlantic.linksys.moosehall> References: <20080610101715.GF5498@atlantic.linksys.moosehall> <20080612100559.GE19396@atlantic.linksys.moosehall> <20080612114705.GG19396@atlantic.linksys.moosehall> <20080613092409.GA8066@atlantic.linksys.moosehall> <0C275B3E-BECB-4A5A-9B95-8C928046DE18@uva.nl> Reply-To: Adam Spiers 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 1K77lJ-0003Rl-GV for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 07:48:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K77lI-0003RI-K1 for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 07:48:09 -0400 Received: from [199.232.76.173] (port=35187 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K77lI-0003RF-Gb for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 07:48:08 -0400 Received: from mail.beimborn.com ([70.84.38.100]:40238) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K77lI-0000aR-A1 for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 07:48:08 -0400 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id m5DBm500029777 for ; Fri, 13 Jun 2008 06:48:05 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id m5DBm5Ur029771 for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 12:48:05 +0100 Content-Disposition: inline In-Reply-To: <0C275B3E-BECB-4A5A-9B95-8C928046DE18@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: org-mode mailing list On Fri, Jun 13, 2008 at 12:28:48PM +0200, Carsten Dominik wrote: > On Jun 13, 2008, at 11:24 AM, Adam Spiers wrote: > >The motivation is that while I very much like org's functionality for > >automatically updating the timestamp on a repeated task once it has > >been marked as done, I do not want tasks such as "water plants" > >cluttering up my calendar forever into the future. I only care about > >the next plant watering, not all others thereafter, and with screen > >real estate always short in supply (especially on mobile devices!), > >any possible savings are of value. > > I can see that this is useful, but I still insist that Org should > export a repeated event as such. As the *default* behaviour, without another behaviour being very specifically requested by the user, I entirely agree :-) > I am adding a hook, `org-before-save-iCalendar-file-hook'. You can > add some special cookie in the headline of the entry, and then > search for this cookie in the exported file and remove the > repetition rule. How about that? Yes thanks; that should do it, and will also possibly enable other use cases via that hook. > >Actually, now I think about it more, the above decluttering argument > >applies equally to the Org agenda itself. So if it would be a more > >consistent request from the point of view of maintaining an intuitive > >UI or from ease of implementation, I would be perfectly happy if the > >proposed property disabled display of all but the first instance of > >the repeated task *everywhere*, i.e. not only in iCal exports, but > >also in agenda displays. > > Org has the variable `org-agenda-repeating-timestamp-show-all' which > allows to modify this behavior for all repeating time stamps, not > for individual ones, though. Well, perhaps you might consider it at some point in the future, or at least a distinction between repeated events and repeated tasks. I think we've now spent enough energy on this relatively minor cosmetic issue though ;-)