From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Showing scheduled blocked tasks Date: Thu, 11 Mar 2010 17:59:05 +0100 Message-ID: References: Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NpmPH-0001af-1Z for emacs-orgmode@gnu.org; Thu, 11 Mar 2010 12:42:47 -0500 Received: from [140.186.70.92] (port=53976 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NpmPF-0001ZQ-NX for emacs-orgmode@gnu.org; Thu, 11 Mar 2010 12:42:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NpmPE-00074e-68 for emacs-orgmode@gnu.org; Thu, 11 Mar 2010 12:42:45 -0500 Received: from mail-ew0-f218.google.com ([209.85.219.218]:38720) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NpmPD-00074I-QH for emacs-orgmode@gnu.org; Thu, 11 Mar 2010 12:42:44 -0500 Received: by ewy10 with SMTP id 10so159557ewy.32 for ; Thu, 11 Mar 2010 09:42:42 -0800 (PST) In-Reply-To: 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: Matthew Phillips Cc: emacs-orgmode@gnu.org Hi Phil, On Mar 11, 2010, at 9:43 AM, Matthew Phillips wrote: > Hi Carsten, > > reply inline below. > > On 11/03/2010, at 4:40 PM, Carsten Dominik wrote: > >> On Mar 11, 2010, at 2:34 AM, Matthew Phillips wrote: >> >>> I am trying to get a TODO tags view in my daily agenda just shows =20= >>> the first TODO of a =93Project=94 (a la the =93next action=94 in = GTD). =20 >>> This allows me to have a TODO =93tags=94 block in my custom agenda =20= >>> that doesn=92t run to several pages: I just see the next action for =20= >>> each project, and, as each action is marked DONE, the next one =20 >>> pops up. >>> >>> I have *almost* managed to get this working by turning on org-=20 >>> enforce-todo-dependencies, setting =93ORDERED: t=94 as a property on = =20 >>> projects, and then using (setq org-agenda-dim-blocked-tasks =20 >>> 'invisible). >>> >>> However, this hides scheduled tasks from the agenda view if they =20 >>> are also blocked (I want them to show up if they are scheduled =20 >>> regardless). It seems that org-agenda-dim-blocked-tasks is not =20 >>> supported as a local setting on custom commands, so I can=92t just =20= >>> make blocked tasks visible in the agenda view and invisible in the =20= >>> TODO tags query. >> >> what do you mean by "is not supported as a local option"? Does =20 >> that mean you miss it in the customize menu for local option, or =20 >> does that mean you have added it using the "any variable" entry and =20= >> then it does not have the desired effect? > > What I mean is setting it as an option in the custom commands does =20 > not seem to work, e.g. see list line in: > > (setq org-agenda-custom-commands > ... > ("d" "Daily Action List" > ((agenda "" ((org-agenda-ndays 1) > (org-agenda-sorting-strategy > (quote ((agenda time-up priority-down tag-up) ))) > (org-deadline-warning-days 7))) > (tags "TODO=3D\"STARTED\"+SCHEDULED=3D\"\"+DEADLINE=3D\"\"" > ((org-agenda-dim-blocked-tasks 'invisible))) > ... > > The org-agenda-dim-blocked-tasks on the generated "tags" view does =20 > not get honoured. It *does* get honoured as a setting one level =20 > "higher", i.e. as a local setting to the whole org-agenda-custom-=20 > commands block, but that's not very useful here. OK, I see now what is happening here. The dimming of blocked tasks is done only once, at the very end, when the agenda has been made. And =20 that is outside the scope of the local options. You can use a normal (custom) agenda command and do the setting there. =20= Or you can use the global options for the block agenda to set this for =20= the entire block agenda. But not for a single segment in a bloc =20 agenda, I am afraid. Changing this would be significant work, and I don't want to do this =20 based on a single use case. - Carsten > >>> IMPORTANT: This email remains the property of the Australian =20 >>> Defence Organisation and is subject to the jurisdiction of section =20= >>> 70 of the CRIMES ACT 1914. If you have received this email in =20 >>> error, you are requested to contact the sender and delete the email. >> >> Wow, this sounds scary. Maybe you need to find a webmail host? :-) > > Heh, well it's all legally binding as soon as you open the email, =20 > just like a EULA you realise? ;) > > This is an unsightly side-effect of posting from an organisation =20 > that blocks webmail, requires the ugly "[SEC=3DUNCLASSIFIED]" for =20 > outside email, and adds that footer automatically. > > Cheers, > > Matthew. - Carsten