From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manish Subject: Re: Weekday repeaters, and filtering scheduled tasks. Date: Thu, 3 Jul 2008 00:17:19 +0530 Message-ID: References: <64F67AD0-E3D4-41A2-8777-9B9F67502F63@uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KE7MW-0007JA-Uj for emacs-orgmode@gnu.org; Wed, 02 Jul 2008 14:47:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KE7MU-0007I6-Fw for emacs-orgmode@gnu.org; Wed, 02 Jul 2008 14:47:27 -0400 Received: from [199.232.76.173] (port=34078 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KE7MU-0007I3-7N for emacs-orgmode@gnu.org; Wed, 02 Jul 2008 14:47:26 -0400 Received: from rv-out-0708.google.com ([209.85.198.247]:35109) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KE7MT-0003jQ-PB for emacs-orgmode@gnu.org; Wed, 02 Jul 2008 14:47:26 -0400 Received: by rv-out-0708.google.com with SMTP id k29so560598rvb.6 for ; Wed, 02 Jul 2008 11:47:24 -0700 (PDT) In-Reply-To: Content-Disposition: inline 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: Carsten Dominik Cc: org-mode mailing list On Wed, Jul 2, 2008 at 11:17 PM, Carsten Dominik wrote: [snip] > which would fail if you did DEADLINE>="" > > There is not good solution for this. uses the date > without a time, in order to provide for comparison with > deadline dates that are only a date, not a time. If your > deadlines have times associated with them, better use a date > and time explicitly. I could provide yesterday and > tomorrow, maybe.... I seem to have found a custom view I am happy with. I am chainging my old approach of scheduling/deadlining every single task. Now I schedule something only if it needs to be done on that day and deadline something only if it's a real deadline/milestone. This leads to a very small (default) agenda view of only essential items. But I wanted to list the tasks currently in progress, list of potential tasks that I can pick up next and remaining the tasks hence the customized agenda below. This view/method also seems to fit nicely with using org-depend to ensure that next sibling gets on the NEXT queue when a task is marked DONE. The old approach of scheduling/deadlining would have required that org-depend/TRIGGER property /schedule/ the next sibling task (just switching the state would not bring it into agenda view.) This also allows me to fiddle with agenda sorting or buffer/subtree restrictions to approach work-list in various ways (e.g. http://www.murtworld.com/2005/04/revolving-workflow-strategies.php). I am not sure how much "" and "" will help in the view below.. we shall see. For now I am okay with these views (and a few exaploratory views.) (setq org-agenda-custom-commands (quote ( ("zu" "NEXT Tasks - No Specified Duration" tags-todo "Effort={^$}/!NEXT-DONE-CANCELLED" nil) ("zz" "My Personalized Agenda" ((agenda "" ((org-agenda-overriding-header "Personalized Agenda:"))) (tags-todo "+SCHEDULED<=\"\"+DEADLINE<=\"\"/!STARTED" ((org-agenda-overriding-header "Currently in progress:"))) (tags-todo "+SCHEDULED<=\"\"+DEADLINE<=\"\"/!NEXT" ((org-agenda-overriding-header "Next in Queue:") (org-agenda-sorting-strategy (quote (category-keep effort-up))))) (tags-todo "+SCHEDULED<=\"\"+DEADLINE<=\"\"/!TODO" ((org-agenda-overriding-header "To be Queued:") (org-agenda-sorting-strategy (quote (category-keep effort-up)))))) nil)))) As always a big thanks for such an amazingly flexible system. Best, -- Manish