From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: iCal export of repeated tasks Date: Fri, 13 Jun 2008 12:28:48 +0200 Message-ID: <0C275B3E-BECB-4A5A-9B95-8C928046DE18@uva.nl> References: <20080610101715.GF5498@atlantic.linksys.moosehall> <20080612100559.GE19396@atlantic.linksys.moosehall> <20080612114705.GG19396@atlantic.linksys.moosehall> <20080613092409.GA8066@atlantic.linksys.moosehall> Mime-Version: 1.0 (Apple Message framework v924) 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 1K76WZ-0005s7-PU for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 06:28:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K76WY-0005qz-Iw for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 06:28:50 -0400 Received: from [199.232.76.173] (port=54987 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K76WY-0005qq-GA for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 06:28:50 -0400 Received: from korteweg.uva.nl ([146.50.98.70]:7657) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K76WY-00005b-0Z for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 06:28:50 -0400 In-Reply-To: <20080613092409.GA8066@atlantic.linksys.moosehall> 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: Adam Spiers Cc: org-mode mailing list On Jun 13, 2008, at 11:24 AM, Adam Spiers wrote: > On Fri, Jun 13, 2008 at 10:18:52AM +0200, Carsten Dominik wrote: >> On Jun 12, 2008, at 1:47 PM, Adam Spiers wrote: >>> Well, I agree that there may not be a good definition, in which >>> case a >>> per-event property disabling export of the RRULE would be a perfect >>> solution. >> >> Hi Adam, >> >> I do not feel comfortable with this specialized filtering, so I am >> not >> implementing it. It seems incorrect that the export of the exact >> same >> Org file would lead to different iCal files, depending on the day >> when >> you do the export. > > Sorry - either I have accidentally misled you, or my understanding is > missing some nuance of your argument, because it was certainly not my > intention to propose a mechanism which would produce different results > depending on when the export is done. I simply wanted to suggest that > there could be a property which would have the same effect upon iCal > export as would manually deleting the directive to repeat ('.+2w' or > similar) from the end of the task's timestamp. This would maintain > the existing behaviour for repeated tasks within Org, but display it > as a non-repeating task in my external calendaring clients > (korganizer, ScheduleWorld, Google Calendar, my Nokia phone etc.) > > 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. 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? > 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. - Carsten