From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andrew M. Nuxoll" Subject: Re: Newbie Questions Date: Thu, 09 Jul 2009 21:08:31 -0700 Message-ID: <4A56BEBF.2080702@up.edu> References: <4A565502.1000808@up.edu> <9547.1247195772@gamaville.dokosmarshall.org> 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 1MP7Pa-00080F-8l for emacs-orgmode@gnu.org; Fri, 10 Jul 2009 00:08:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MP7PV-0007xe-Kr for Emacs-orgmode@gnu.org; Fri, 10 Jul 2009 00:08:37 -0400 Received: from [199.232.76.173] (port=59004 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MP7PV-0007xb-Az for Emacs-orgmode@gnu.org; Fri, 10 Jul 2009 00:08:33 -0400 Received: from egateone.up.edu ([64.251.254.100]:47666) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MP7PU-0006bs-Sh for Emacs-orgmode@gnu.org; Fri, 10 Jul 2009 00:08:33 -0400 In-Reply-To: <9547.1247195772@gamaville.dokosmarshall.org> 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 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! > So let me turn the question around: why do you need to both SCHEDULE > and DEADLINE the same item? > 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. 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. > >> 2. Once a TODO item has been marked as DONE, it still shows up on my >> agenda. Can this be avoided? > I believe this was answered already. > Yes it was. Thanks, Brian.