From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matt Lundin <mdl@imapmail.org>
Subject: Re: Visual indication on unscheduled TODOs
Date: Wed, 01 Dec 2010 20:31:25 -0500
Message-ID: <87aakp6jv6.fsf@fastmail.fm>
References: <AANLkTimmtGvzfykZ_e3fTOkdTtcgESOxxDCC7WroGjGe@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=34169 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PNy1B-0001QI-Ni
	for emacs-orgmode@gnu.org; Wed, 01 Dec 2010 20:31:30 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1PNy1A-0006TU-Hp
	for emacs-orgmode@gnu.org; Wed, 01 Dec 2010 20:31:29 -0500
Received: from out1.smtp.messagingengine.com ([66.111.4.25]:41244)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1PNy1A-0006TI-G4
	for emacs-orgmode@gnu.org; Wed, 01 Dec 2010 20:31:28 -0500
In-Reply-To: <AANLkTimmtGvzfykZ_e3fTOkdTtcgESOxxDCC7WroGjGe@mail.gmail.com>
	(Martin Svenson's message of "Wed, 1 Dec 2010 21:30:45 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Martin Svenson <phromo@mail.com>
Cc: emacs-orgmode@gnu.org

Martin Svenson <phromo@mail.com> writes:

> I'm trying to get a visual hint that a certain TODO is unscheduled, so
> that I can immediately see this when I go through the outline during
> regular reviews.
> ...

> ...but I get the nagging feeling I'm going about this the wrong way.
> Surely, being able to see which items are due for scheduling is a
> common task? (I do note that I could search for them, but then I would
> not have the context of the actually scheduled tasks in the same
> view...)

Within an org buffer, I would use a sparse tree:

C-c / m 
-SCHEDULED={.}/!

This tells org to highlight anything that does not have a scheduled
property. The "/!" tells Org to limit the search to active todos.

To see all unscheduled todos across my agenda files, I would use:

--8<---------------cut here---------------start------------->8---
(add-to-list 'org-agenda-custom-commands
	     '("u" "Unscheduled" alltodo ""
	       ((org-agenda-todo-ignore-scheduled t))))
--8<---------------cut here---------------end--------------->8---

Best,
Matt