From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: Agenda of upcoming deadlines skips some deadlines Date: Tue, 14 Jun 2011 21:36:22 +0200 Message-ID: References: <80sjrls2ll.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:49025) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWZPW-00085N-Ib for emacs-orgmode@gnu.org; Tue, 14 Jun 2011 15:36:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QWZPU-0005CZ-PA for emacs-orgmode@gnu.org; Tue, 14 Jun 2011 15:36:26 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:52002) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWZPU-00059z-AQ for emacs-orgmode@gnu.org; Tue, 14 Jun 2011 15:36:24 -0400 Received: by eyd9 with SMTP id 9so2514960eyd.0 for ; Tue, 14 Jun 2011 12:36:23 -0700 (PDT) In-Reply-To: <80sjrls2ll.fsf@somewhere.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastien Vauban Cc: emacs-orgmode@gnu.org Hi Sebastien On Wed, Jun 8, 2011 at 00:23, Sebastien Vauban wrote: > #+begin_src emacs-lisp > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0("F" "Agenda of upcoming deadlines (6 mont= hs)" > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 agenda "" > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ((org-agenda-ndays 1) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-deadline-warning-days 183) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-include-all-todo nil) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-time-grid nil) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-skip-function > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 '(org-agenda-skip-entry-if 'notdeadli= ne)))) > #+end_src 1) "C-h v org-agenda-ndays" says: "This variable is obsolete since 24.1; use `org-agenda-span' instead." and "Obsolete, see `org-agenda-span'." 2) "C-h v org-agenda-include-all-todo" says: "This option is deprecated, it is better to define a block agenda instead."... ...when you want to add TODO items. In your case I would simply leave it out. 3) Instead of _skipping_ "notadeadline" I would recommend to _choose_ ":deadline" with: (org-agenda-entry-types '(:deadline)) > - future tasks that have *an explicit warning specification* are skipped! > > =A0Example: > > =A0* TODO Change car insurance > =A0 =A0DEADLINE: <2011-09-04 Sun -1m> > > =A0is not shown because of the "-1m" (my default is 14 days, but I found = that > =A0too little in this case). This item overrides the (org-deadline-warning-days 183) from the custom agenda command with one month from DEADLINE and the item will be shown the first time on 2011-08-04. But as I tried to understand, you want to see all DEADLINES of the next 183 days, however their individual warning period might even not have started yet, right? For this I suggest to try out an agenda custom command with: (org-agenda-span 183) (org-deadline-warning-days 0) This agenda view will probably come along with 183 headers for the date of each day, which I don't know how to disable for the empty days. I fear there is nothing yet like org-timeline-show-empty-dates for agenda blocks, check if it works. But anyhow, the agenda view is better used with a smaller agenda span like one month (keys "v m") or only one week (key "w") together with the keys "f" and "b" for scrolling. You could also go into the direction of a plain search with something like DEADLINE<=3D\"<+183d>\" with maybe an undesired ordering. Many search examples are explained here: http://orgmode.org/manual/Matching-tags-and-properties.html#Matching-tags-a= nd-properties > - scheduled tasks (in the past and/or for today) are shown, when paired w= ith a > =A0deadline'd task. > > =A0Example: > > =A0* TODO Change of insurance company > =A0 =A0DEADLINE: <2011-09-04 Sun> > =A0 =A0SCHEDULED: <2011-06-06 Mon> I have stopped to combine SCHEDULED with DEADLINE (shown twice, as DEADLINE and as SCHEDULED) and for tasks of this kind I always use DEADLINE with an explicit warning period, not necessarily with TODO. For the latter example: : * Check whether to change insurance company : DEADLINE: <2011-09-04 Sun -90d> This will not be shown earlier than 2011-06-06, like an item that is SCHEDULED on 2011-06-06. From then on it will be shown as a DEADLINE until it will either be removed from the agenda file or set to a new DEADLINE date in e. g. next year. For all items with an active timestamp I use TODO only if there is a repeating period like "+1y" together with DEADLINE or SCHEDULED: : * TODO Check whether to change insurance company : DEADLINE: <2011-09-04 Sun +1y -90d> Changing this to DONE with "C-c C-t" will do the reschedule automatically and switch back to TODO, updated in the agenda after "g". Michael