From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: org mode vs basecamp Date: Wed, 24 Oct 2007 13:05:19 +0100 Message-ID: <87fy00en0g.fsf@bzg.ath.cx> 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> <87lk9sbx8o.fsf@myhost.localdomain> 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 1Ike36-0005E2-1T for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 07:05:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ike34-0005AV-AZ for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 07:05:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ike34-0005AE-6y for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 07:05:18 -0400 Received: from ug-out-1314.google.com ([66.249.92.175]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ike33-0005TD-Gr for emacs-orgmode@gnu.org; Wed, 24 Oct 2007 07:05:17 -0400 Received: by ug-out-1314.google.com with SMTP id a2so328103ugf for ; Wed, 24 Oct 2007 04:05:16 -0700 (PDT) In-Reply-To: <87lk9sbx8o.fsf@myhost.localdomain> (cezar@mixandgo.ro's message of "Wed, 24 Oct 2007 13:52:39 +0300") 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 cezar@mixandgo.ro writes: > 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. Sorry I didn't express myself very well. Of course Org already know how to export an .org file to .ics. My point was: if you want to use the ouput .ics file as a basis for collaboration then you might want that Org export keywords like ATTENDEE in the .ics file. As I added in the footnote, I think the set of properties that Org will export for each iCal entry should be customizable, because people might have different properties for the same .ics keywords, or might want to skip keywords that are not relevant to their use of the .ics file. >> [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. No, this is not what I mean. I was saying that the set of keywords (those necessary to use the .ics file as a basis for collaboration) should not be rigid, if such keywords are to be implemented someday. I was not speaking about something that already exists. But maybe what i said will be clearer if you try to use the .ics file for collaboration. Don't forget to make a tutorial of how successful you were in doing this :) -- Bastien