From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Schedule event Date: Wed, 24 Aug 2011 12:26:24 +0200 Message-ID: <87vctnds1b.fsf@gnu.org> References: <877h6raiwc.fsf@riotblast.dunsmor.com> <8739hc98rp.fsf@riotblast.dunsmor.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:55382) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwAeX-0002q6-LI for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 06:25:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QwAeW-00026I-CF for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 06:25:45 -0400 Received: from mail-fx0-f41.google.com ([209.85.161.41]:63827) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwAeW-00025y-3y for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 06:25:44 -0400 Received: by fxg9 with SMTP id 9so1038588fxg.0 for ; Wed, 24 Aug 2011 03:25:43 -0700 (PDT) In-Reply-To: <8739hc98rp.fsf@riotblast.dunsmor.com> (Jason Dunsmore's message of "Sun, 07 Aug 2011 17:06:18 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jason Dunsmore Cc: Carsten Dominik , emacs-orgmode@gnu.org Hi Jason, Jason Dunsmore writes: > Carsten Dominik writes: > >> Why do you want this special interface for setting an event date. >> How is that better than `C-c .'? Is it that you don't need to >> position the cursor? > > Yes, that was my original reason. But your suggestion of adding a > special keyword for events is another good reason. Also, as recently > discussed, consistent formatting conventions and clarifying the > frequently-misunderstood issue of SCHEDULED vs. no-keyword active > timestamps are good reasons. I agree adding an EVENT: (or "APPT:") would be nice. What I suggest is this: 1. merge org-schedule and org-deadline into a new org-plan function. 2. allow org-plan to set a new org-schedule-special keyword (this keyword would be "EVENT" by default, but customizable.) Now I'm unclear yet whether the set of features that is available for scheduled entries should also return special-keyword entries (e.g. org-agenda-get-scheduled) or if this should be a completely separate set of features -- in which case I have the feeling we are really emulating the use of an :EVENT: property. What is your take on this? Thanks for bringing this up anyway! PS: it took me long to reply because I'm also considering using the property drawer to store timestamps like SCHEDULED, DEADLINE and so on. But it is a big move and we can't delay your request by relying on such a change. -- Bastien