From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Maus Subject: Re: Re: Contracts in Orgmode Date: Thu, 24 Dec 2009 10:22:43 +0100 Message-ID: <87y6ksafq4.wl%maus.david@gmail.com> References: Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NNjuI-0007e0-Ht for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 04:22:54 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NNjuD-0007YM-AN for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 04:22:53 -0500 Received: from [199.232.76.173] (port=55737 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NNjuD-0007Y3-3v for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 04:22:49 -0500 Received: from mail-ew0-f224.google.com ([209.85.219.224]:43636) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NNjuC-0002JW-JW for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 04:22:48 -0500 Received: by ewy24 with SMTP id 24so9131541ewy.26 for ; Thu, 24 Dec 2009 01:22:46 -0800 (PST) In-Reply-To: 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: Markus Heller Cc: emacs-orgmode@gnu.org At Tue, 22 Dec 2009 13:49:07 -0800, Markus Heller wrote: > > > After some more googling and having a closer look at the org manual, I > came up with a solution that might work. It uses dependencies and > org-depend.el. I've pasted it below, and as usual, I'd appreciate any > comments/improvement :) > > I realize that this is not exactly an elegant solution, but it might > work for me. I'd still like to see a way in orgmode to allow clocking > in on certain tasks only during a specific period of time, maybe > something like > > ** Contract for Client A > :PROPERTIES: > :START: 01-01-2010 > :EXPIRY: 03-31-2010 > :END: > > Then, when the START date is reached, the task state gets changed to the > TODO or STARTED, and once the expiry date is reached, it gets marked > DONE, and cannot be clocked in anymore. I'm not sure if this is a > feature that would be of general interest ... But what do the experts > think? With regards to closing expired items you may take a look at org-expiry.el in the contrib directory. It provides a function to check for and act upon entries that are past their expiration date. What I am not quite understanding is the wish to be unable to clock in a closed item: Isn't clocking in something you do deliberately? Regards -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber.... dmjena@jabber.org Email..... maus.david@gmail.com ICQ....... 241051416