From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: postponing todos Date: Tue, 07 Aug 2007 02:56:23 +0200 Message-ID: <87643s9n7s.fsf@bzg.ath.cx> References: <878x8osm96.fsf@freemail.hu> <87tzrcfe16.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IIDNO-00028l-Iw for emacs-orgmode@gnu.org; Mon, 06 Aug 2007 20:56:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IIDNL-00028Z-TD for emacs-orgmode@gnu.org; Mon, 06 Aug 2007 20:56:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IIDNL-00028W-Np for emacs-orgmode@gnu.org; Mon, 06 Aug 2007 20:56:43 -0400 Received: from hu-out-0506.google.com ([72.14.214.226]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IIDNJ-0002h9-5D for emacs-orgmode@gnu.org; Mon, 06 Aug 2007 20:56:42 -0400 Received: by hu-out-0506.google.com with SMTP id 23so1292092huc for ; Mon, 06 Aug 2007 17:56:28 -0700 (PDT) In-Reply-To: <87tzrcfe16.fsf@bzg.ath.cx> (Bastien's message of "Tue\, 07 Aug 2007 01\:18\:13 +0200") 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 Bastien writes: >> I would like to quickly (by using shortcuts) postpone a todo entry from >> the agenda buffer by: >> - 1-2-3 day >> - coming monday/friday >> - next monday/friday >> >> What is possible with current org mode? > > I don't think so, and i'm not sure on how it could be implemented. > > Maybe a :WarningAtDay: property? Conceptually this requires that we're > able to distinguish between postponing the date a todo is displayed on > and postponing the todo itself (the day it's supposed to be done)... > All this might be a bit confusing. Trying to think further, i stumbled on this idea: what about having something like an _AGENDA suffix for properties that would make the agenda decide whether it should get the entry or not? For example, here is a todo: ,---- | * Try to avoid stupid examples | :PROPERTIES: | :WarningAtDay_AGENDA: <2007-11-11 dim> | :END: `---- When getting entries for the agenda display, Org might an entry with such a _AGENDA property. Then Org's job would be to check whether this entry has to be included in the results or not. For doing so, it will have to call a user-defined function like : ,---- | (defun org-agenda-get-entry:WarningAtDay (param) | ... | [Returns t or nil depending on param] | ...) `---- If the function returns t (e.g. if the function above says that today is later than the value of WarningAtDay_AGENDA), then the todo is included. This way each user could (easily) define its own rules for deciding what entries should appear in the agenda display. But enough speculation for tonight :) -- Bastien