From mboxrd@z Thu Jan 1 00:00:00 1970 From: cezar@mixandgo.ro Subject: Re: org mode vs basecamp Date: Wed, 24 Oct 2007 13:52:39 +0300 Message-ID: <87lk9sbx8o.fsf@myhost.localdomain> References: <87myuaxk9y.fsf@myhost.localdomain> <877ild4v1s.fsf@bzg.ath.cx> <87myu9eknl.fsf@myhost.localdomain> <87prz5zin1.fsf@bzg.ath.cx> <87prz4c24s.fsf@myhost.localdomain> <871wbk4xlp.fsf@bzg.ath.cx> 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 1Ikdsc-0002Le-3z for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 06:54:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IkdsW-0002Cw-Jj for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 06:54:28 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IkdsV-0002BI-JQ for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 06:54:23 -0400 Received: from main.gmane.org ([80.91.229.2] 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 1IkdsU-0000KG-SB for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 06:54:23 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IkdsO-00018r-3z for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 10:54:16 +0000 Received: from dyn-86.105.65.100.tm.upcnet.ro ([86.105.65.100]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Oct 2007 10:54:16 +0000 Received: from cezar by dyn-86.105.65.100.tm.upcnet.ro with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Oct 2007 10:54:16 +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 Bastien writes: > which might be added to Org[1] so that an .org file can be exported in > .ics and so that this .ics resource can be useful as a shared resource > for collaboration. You can already use it like this (i do), but maybe > some other keywords (like the two above) would be nice to have. I think we can allready export to ics ! I remember doing it. In the agenda view. > >> I am not too familiar with them but I think they pretty much do what I >> need !? > > But the .ics solution still requires that you answer this question: who > is able to edit the .org source file(s)? > > Notes: > [1] I'm not sure this as to be native in Org. Maybe an option saying > what property of en entry should be exported to a .ics keyword is > needed at some point. Maybe scan todo.ics at start time ? to see if anything was added. An ics file could also be populated by either a custom app or google calendar ir any other app that understands ics.