From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: org-mode and Google Calendar Date: Thu, 04 Oct 2007 11:44:34 +0100 Message-ID: <87fy0rjh0t.fsf@bzg.ath.cx> References: <87d4w3s1pb.fsf@myhost.localdomain> <87abr6zwmg.fsf@bzg.ath.cx> <87641ttx8w.fsf@bzg.ath.cx> <871wchsgc1.fsf@bzg.ath.cx> <403a8bd9e84288d3a69dbdee1fc2dc82@science.uva.nl> 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 1IdOCD-0003xQ-0t for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 06:44:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IdOC9-0003sJ-Fa for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 06:44:44 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IdOC9-0003s7-AW for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 06:44:41 -0400 Received: from mu-out-0910.google.com ([209.85.134.188]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IdOC8-0006vs-UM for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 06:44:41 -0400 Received: by mu-out-0910.google.com with SMTP id g7so166643muf for ; Thu, 04 Oct 2007 03:44:40 -0700 (PDT) In-Reply-To: <403a8bd9e84288d3a69dbdee1fc2dc82@science.uva.nl> (Carsten Dominik's message of "Thu, 4 Oct 2007 09:56:19 +0200") 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 Carsten Dominik writes: >> And maybe this description field could also skip timestamps that are >> not >> SCHEDULED or DEADLINE. I often use such timestamps and the description >> shows them, which looks weird: >> >> DESCRIPTION: <2007-12-19 mer> > > Not sure about that, how to decide what is important and what not? Yes, no need to skip timestamp when getting the description. I just discovered I could use timestamps in properties like this: :PROPERTIES: :TIMESTAMP: <2007-10-04 jeu> :SCHEDULED: <2007-10-04 jeu> :DEADLINE: <2007-10-04 jeu> :ARCHIVE: archives/patres_archive:: :CATEGORY: patres :END: This way the description doesn't contain the timestamp. Maybe a :DESCRIPTION: would also be useful to explicitly specify the short description. This short description would override the one that Org tries to guess from the first line of the subtree. But eh, I've got my :LOCATION: so I won't be pushy on this one :) -- Bastien