From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Heller Subject: Re: Contracts in Orgmode Date: Thu, 24 Dec 2009 10:35:58 -0800 Message-ID: References: <87y6ksafq4.wl%maus.david@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NNsY7-0002oI-2b for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 13:36:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NNsY2-0002iQ-QX for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 13:36:34 -0500 Received: from [199.232.76.173] (port=46035 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NNsY2-0002i1-IP for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 13:36:30 -0500 Received: from lo.gmane.org ([80.91.229.12]:56613) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NNsY2-0002D9-Ff for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 13:36:30 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NNsXu-0006B2-FR for emacs-orgmode@gnu.org; Thu, 24 Dec 2009 19:36:22 +0100 Received: from mail.cdrd.ca ([142.103.191.98]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Dec 2009 19:36:22 +0100 Received: from hellerm2 by mail.cdrd.ca with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Dec 2009 19:36:22 +0100 In-Reply-To: <87y6ksafq4.wl%maus.david@gmail.com> 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 On 12/24/2009 1:22 AM, David Maus wrote: > 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. Thanks. I'll have a look at it. > 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? Work should only be done if a valid contract exists (no valid contract, no payment, right? :) ). Right now, my work flow is to bring up an agenda view with all STARTED items, and then I'd clock in on the Contract. I'm not aware of how to check if the contract is valid or not, so I might be clocking in on an expired contract. Is there a way to include an expiry flag in the agenda view? Maybe there can be a regexp in the PROPERTIES that checks if the actual date is before the expiry date? If that was the case, then that would let me see right away in the agenda view if I'm about to clock in on an expired contract. I hope I'm not too confusing in my description of what I'm trying to achieve ... In any case, merry xmas to all of you! Markus