From mboxrd@z Thu Jan 1 00:00:00 1970 From: knubee Subject: Re: icalender export: limited number of repeated events Date: Tue, 17 Jun 2008 01:35:59 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K8Q7J-0002GW-0A for emacs-orgmode@gnu.org; Mon, 16 Jun 2008 21:36:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K8Q7I-0002G2-ET for emacs-orgmode@gnu.org; Mon, 16 Jun 2008 21:36:12 -0400 Received: from [199.232.76.173] (port=49802 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K8Q7I-0002Fs-Bv for emacs-orgmode@gnu.org; Mon, 16 Jun 2008 21:36:12 -0400 Received: from main.gmane.org ([80.91.229.2]:42206 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K8Q7H-00065h-Uc for emacs-orgmode@gnu.org; Mon, 16 Jun 2008 21:36:12 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1K8Q7D-0001Je-Vi for emacs-orgmode@gnu.org; Tue, 17 Jun 2008 01:36:10 +0000 Received: from 218-186-11-3.cache.maxonline.com.sg ([218-186-11-3.cache.maxonline.com.sg]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 Jun 2008 01:36:07 +0000 Received: from knubee by 218-186-11-3.cache.maxonline.com.sg with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 Jun 2008 01:36:07 +0000 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: emacs-orgmode@gnu.org > However, I did not know that the icalendar format actually supported > something like UNTIL in the RRULE line. So maybe we could teach the Org > exporter a syntax for this and export it properly. However, I don't > have a good idea for a syntax, and not much time to implement it now. ok. it does seem like a fairly standard thing to do with calendars (ie, to have repeating events that end after a certain number -- or after a certain date). perhaps, in the future, it is worth implementing something that allows org-mode user to specify something lik: SCHEDULED: <2008-06-01 Sun +1w~10> ;repeats until 10 weeks after starting date or SCHEDULED: <2008-06-01 Sun +1w~2008-08-03> ;repeats until august 3 the actual symbols ("~") and syntax used above are probably bad, but hopefully it captures the idea. > - When you are done, share this with us! it may be a bit beyond my abilities, but if i get something to work, i will share it ;-)