emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Martin Svenson <phromo@mail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Visual indication on unscheduled TODOs
Date: Wed, 01 Dec 2010 20:31:25 -0500	[thread overview]
Message-ID: <87aakp6jv6.fsf@fastmail.fm> (raw)
In-Reply-To: <AANLkTimmtGvzfykZ_e3fTOkdTtcgESOxxDCC7WroGjGe@mail.gmail.com> (Martin Svenson's message of "Wed, 1 Dec 2010 21:30:45 +0100")

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

  reply	other threads:[~2010-12-02  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 20:30 Visual indication on unscheduled TODOs Martin Svenson
2010-12-02  1:31 ` Matt Lundin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-01 20:29 Martin Svenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87aakp6jv6.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=phromo@mail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).