|Subject:||Re: [Orgmode] Newbie Questions|
|Date:||Fri, 10 Jul 2009 08:06:04 +0100|
|User-agent:||Thunderbird 126.96.36.199 (X11/20090608)|
Andrew M. Nuxoll wrote:
Nick Dokos wrote:Just an FYI (a nice one since Carsten said so :-): Carsten is the first name, Dominik (no c) is the surname of the creator of Org-mode. And I promise we'll be nice even after he comes back :-)Err, whoops!In my mind, there is no conflict between scheduling and deadlining. So, I may be missing something. In my case, I am scheduling myself to work on an item that has a deadline. I don't think that's an unusual scenario. For example, I have a grant proposal I need to have a draft of by Monday (DEADLINE) but I've scheduled Thursday afternoon to work on it. By putting SCHEDULED on it means that it gets attention on that day unless Murphy steps in. If Murphy does, then I still have the benefit of the DEADLINE to keep me apprised of my dire situation.So let me turn the question around: why do you need to both SCHEDULE and DEADLINE the same item?An alternative (which I don't like) is to not use DEADLINE on a SCHEDULED item. Instead, I can just attach a second date to the item and label it "deadline" or "drop dead date." So, the best option I have now is to ignore the double entry. I was hoping there was a magic variable(TM) for this like there was with the other issue.
You could specify a per deadline warning period. The example for the manual: DEADLINE: <2004-02-29 Sun -5d>, which will start prompting you 5 days before the deadline. I use this to remind me that I need to start working on something which has a fixed deadline.
|[Prev in Thread]||Current Thread||[Next in Thread]|