From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Riley Subject: Re: Occurance property, or some similar name? Date: Tue, 12 Apr 2011 22:24:50 +0200 Message-ID: References: <87d3ksqujv.fsf@dustycloud.org> <874o63tgg5.fsf@mean.albasani.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:43330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9pGy-0002b6-Vi for emacs-orgmode@gnu.org; Tue, 12 Apr 2011 21:53:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q9k9r-00077D-TI for emacs-orgmode@gnu.org; Tue, 12 Apr 2011 16:25:57 -0400 Received: from lo.gmane.org ([80.91.229.12]:54601) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9k9r-00076j-I9 for emacs-orgmode@gnu.org; Tue, 12 Apr 2011 16:25:55 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Q9k9m-000420-Ti for emacs-orgmode@gnu.org; Tue, 12 Apr 2011 22:25:50 +0200 Received: from 85.183.18.158 ([85.183.18.158]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Apr 2011 22:25:50 +0200 Received: from rileyrg by 85.183.18.158 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Apr 2011 22:25:50 +0200 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: emacs-orgmode@gnu.org Memnon Anon writes: > Hi, > Christopher Allan Webber writes: > >> I was once one of the many people who apparently originally >> misunderstood what "SCHEDULED" meant, and used to set it to like, an >> appointment time. > > Well, you can use it that way. > The point is: Scheduled items behave differently to timestamped items. > If you prefer the behaviour scheduling provides you with, go for it. > >> I kind of miss how nice it was back when I misunderstood how events work >> (escept for all of those non-TODOs staying around forever on my >> agenda..) where I had a dedicated property for this, and pressing >> C-c C-s would always change that property. > > I just did a quick check. > It seems to me that timestamps within a property work. > So, if you prefer, you can set your timestamps in a property like this: > > * NEXT Task 2 > :LOGBOOK: > :END: > :PROPERTIES: > :DATE: <2011-04-12> > :END: Yup, its what i use to make sure my journal entries appear in my agenda, the snipped from org-capture-templates is ("j" "Journal" entry (file+datetree "journal.org") "* %?\n :PROPERTIES:\n :DateCreated: %T\n :END:\n%i\n%a") very handy.