From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: Patch: More options for ignoring scheduled items in agenda todo lists Date: Fri, 14 Jan 2011 07:52:33 -0500 Message-ID: <878vynsl4e.fsf@fastmail.fm> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=37226 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pdj8w-0001ZJ-N8 for emacs-orgmode@gnu.org; Fri, 14 Jan 2011 07:52:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pdj8u-0007mO-BO for emacs-orgmode@gnu.org; Fri, 14 Jan 2011 07:52:38 -0500 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:53398) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pdj8u-0007mH-7S for emacs-orgmode@gnu.org; Fri, 14 Jan 2011 07:52:36 -0500 In-Reply-To: (Paul Sexton's message of "Thu, 13 Jan 2011 22:46:14 +0000 (UTC)") 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: Paul Sexton Cc: emacs-orgmode@gnu.org Hi Paul, Paul Sexton writes: > In agenda todo lists, currently it is possible to ignore scheduled > items according to when they are scheduled, using the variable > 'org-agenda-todo-ignore-scheduled'. This can take one of three > values - all, future (ignore if scheduled after today), or past > (ignore if scheduled TODAY or in the past). > > My definition of 'the past' does not include 'today'. > In light of that, the following is a patch that makes the variable > accept 2 more values: > - notpast: ignore if scheduled today or in the future > - notfuture: ignore if scheduled today or in the past > (this is the current behaviour of the 'past' setting) > - past: changed to ignore if scheduled BEFORE today, but no > longer ignores items scheduled today. > I believe this patch would require many users to change their existing configurations. I rely on the "past" setting when creating block agenda views, such as an agenda that includes everything scheduled today or earlier together with a todo list that includes everything else (i.e., unscheduled or scheduled in the future). If the definition of past is changed, I will end up with a lot of duplicate items in the block agenda. Also, I find the double negatives a bit difficult to get my mind around. Would there perhaps be a way to generalize this functionality (e.g., with integers) that would allow users greater control over the precise distance from the present they would like to skip? E.g., -1 to include only items scheduled yesterday or earlier. Or 7 to ignore anything scheduled later than a week from now. This could be quite useful and would not require users to change their existing configurations. Do you also plan to make adjustments for org-agenda-todo-ignore-deadlines? Best, Matt