From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Newbie Questions Date: Thu, 09 Jul 2009 23:16:12 -0400 Message-ID: <9547.1247195772@gamaville.dokosmarshall.org> References: <4A565502.1000808@up.edu> Reply-To: nicholas.dokos@hp.com Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MP6u5-0003QS-3R for emacs-orgmode@gnu.org; Thu, 09 Jul 2009 23:36:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MP6tz-0003PF-Tz for emacs-orgmode@gnu.org; Thu, 09 Jul 2009 23:36:03 -0400 Received: from [199.232.76.173] (port=33755 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MP6tz-0003PC-OO for emacs-orgmode@gnu.org; Thu, 09 Jul 2009 23:35:59 -0400 Received: from vms173019pub.verizon.net ([206.46.173.19]:34716) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MP6tz-0008LB-Di for emacs-orgmode@gnu.org; Thu, 09 Jul 2009 23:35:59 -0400 Received: from gamaville.dokosmarshall.org ([98.110.172.221]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KMJ00M8LR8OCPY3@vms173019.mailsrvcs.net> for emacs-orgmode@gnu.org; Thu, 09 Jul 2009 22:34:05 -0500 (CDT) In-reply-to: Your message of "Thu, 09 Jul 2009 13:37:22 PDT." <4A565502.1000808@up.edu> 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: "Andrew M. Nuxoll" Cc: emacs-orgmode@gnu.org Andrew M. Nuxoll wrote: > Also, Dominick said you had to be nice to me while he was away. > 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 :-) > 1. When I view my agenda for a day it displays TODO items twice if they > are both SCHEDULED and DEADLINEd (a common occurrence for me). Can this > be avoided? Here's a generic example snippet from my agenda: > Thursday 9 July 2009 > nux: Scheduled: TODO [#B] Call Mary :PROJECT:: > nux: In 1 d.: TODO [#B] Call Mary :PROJECT:: > I think you SCHEDULE an item on a given day, in order to start working on it on that day. There is generally no penalty for taking perhaps a long time to finish it, or rescheduling it for a later time. All that happens is that at some point in the future it'll pop up in the agenda. DEADLINE on the other hand implies a penalty: if you don't finish it by the deadline, something bad is going to happen. It then starts appearing in the agenda a few days before the actual deadline to remind you of the dire consequences, should you miss the deadline. How many days before is controllable either by a global variable or by modifying the timestamp (see section 8.3 of the manual: Deadlines and Scheduling). Apologies if you already know the details, but I wanted to highlight the difference between these two. So let me turn the question around: why do you need to both SCHEDULE and DEADLINE the same item? > 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. > > Meta-Comments on Questions 1&2: I realize I have the option of using > the "ToDo Items" agenda view instead of the day/week agenda view but > that doesn't work for me because I use the SCHEDULED property as a way > of selecting a small subset of tasks for the day from a long list of > TODO items. I also rely heavily upon repeating tasks to automate most > of this. So maybe the solution to #1 and #2 is to use a custom agenda > of some sort but I don't see an obvious way to create one that does what > I want. > > 3. Once I set a deadline for a task, it'd be nice if the priority would > increase as the deadline approached. Ideally the criteria for > increasing the priority could be specified via a customizable formula. > Does this functionality (or anything like it) exist? > I don't think anything like that exists, but with a Small[1] Amount of Programming (TM), it could probably be cobbled up - maybe as a cron job? Nick [1] OK, maybe not so small...