From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric S Fraga Subject: Re: ical2org (better timezone recognition and better default for max_age option) Date: Wed, 23 Feb 2011 20:44:57 +0000 Message-ID: <87vd0a1nw6.fsf@ucl.ac.uk> References: <4D490193.8070708@lbl.gov> <87k4hionz0.fsf@pinto.chemeng.ucl.ac.uk> <4D5CCE9F.4000309@lbl.gov> <87oc6233io.fsf@ucl.ac.uk> <4D656DFD.1020106@lbl.gov> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=50797 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PsLa6-0007K3-Tj for emacs-orgmode@gnu.org; Wed, 23 Feb 2011 15:45:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PsLa4-00021j-Ha for emacs-orgmode@gnu.org; Wed, 23 Feb 2011 15:45:06 -0500 Received: from vscane-a2.ucl.ac.uk ([144.82.108.42]:40720) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PsLa4-00021G-DW for emacs-orgmode@gnu.org; Wed, 23 Feb 2011 15:45:04 -0500 In-Reply-To: <4D656DFD.1020106@lbl.gov> (Arun Persaud's message of "Wed, 23 Feb 2011 12:28:45 -0800") 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: Arun Persaud Cc: emacs-orgmode@gnu.org Arun Persaud writes: > Hi > >> however, I'm a little concerned with some of the other changes, >> specifically that all timed events have become scheduled todo >> entries (of type GCAL) which really doesn't fit in with my use case >> at all unfortunately. > > probably should make this configurable. How about defining a string that > is attached to all entries, this could then be "GCAL", "TODO" or just > empty "". yes, that would be good. You should aim to keep the configuration options defined directly in the file to a minimum or at least configurable at run time. > The reason that I added the GCAL is that when I want to exclude them > from being exported back into google, so a tag worked fine, but I guess > this could also be done in other ways. the whole point of the UID field was to ensure that any entries exported back would be ignored as google will treat any such entry as already there if the id matches one of the entries. >> I think scheduled events should be restricted to TODO entries -- >> maybe it's a matter of figuring out how google exports tasks and keep >> diary entries as just that? > > I'm not using google tasks or emacs diary, so I can't really say how > this would work No, sorry, not the Emacs Diary/Calendar but entries that appear in the org agenda view simply as timed entries. E.g. something like #+begin_src org * meeting with my students <2011-02-24 Thu 11:00-11:30> #+end_src will appear in the agenda for that day and that time. As soon as you "schedule" something, it becomes a "task" and it will continue to appear on following days until you mark the "task" as done. This is very different from a simple timed entry in the agenda. For timed entries (or all day entries) from google, the direct mapping in org is simple headings with /active/ time stamps. There is no need for the SCHEDULED specification. >> I do like that you are picking up the LOCATION and STATUS fields. I >> wonder if these could be made into properties for the org headlines >> you create, much as is done with the UID entry? > > should be easy. Yes, simply move the two output statements for these to where the "id" information is written out. Thanks, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.4 (release_7.4.529.gb23d.dirty)