From: David Maus <maus.david@gmail.com>
To: Markus Heller <hellerm2@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Contracts in Orgmode
Date: Thu, 24 Dec 2009 10:22:43 +0100 [thread overview]
Message-ID: <87y6ksafq4.wl%maus.david@gmail.com> (raw)
In-Reply-To: <hgresk$22l$1@ger.gmane.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
next prev parent reply other threads:[~2009-12-24 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 19:16 Contracts in Orgmode Markus Heller
2009-12-21 22:18 ` Daniel Martins
2009-12-22 21:49 ` Markus Heller
2009-12-24 9:22 ` David Maus [this message]
2009-12-24 18:35 ` Markus Heller
2009-12-24 18:52 ` Markus Heller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6ksafq4.wl%maus.david@gmail.com \
--to=maus.david@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hellerm2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).