emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: emacs-orgmode@gnu.org
Subject: Sparse tree for undated TODOs, or hierachical agenda?
Date: Fri, 17 Apr 2015 20:35:04 -0700	[thread overview]
Message-ID: <87fv7yhzx3.fsf@vostro.rath.org> (raw)

Hello,

I'm starting to like orgmode more and more. Thanks for working on this!

However, for me the global todo list in the Agenda very hard to digest
(even when excluding sublevels), so I'd rather have a view that
conserves the document structure.

Is there a way to create a sparse tree that shows only undated TODOs
(i.e., excludes anything that scheduled or has a deadline)?

Or, alternatively, is there a way to generate an Agenda view that
preserves the outline of the document (i.e., TODO items are grouped by
their headings)?

Thanks,
-Nikolaus
-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

             reply	other threads:[~2015-04-18  3:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-18  3:35 Nikolaus Rath [this message]
2015-04-21  1:16 ` Sparse tree for undated TODOs, or hierachical agenda? Nikolaus Rath
2015-04-21 14:10 ` Jorge A. Alfaro-Murillo
2015-04-21 15:35   ` Nikolaus Rath
2015-04-21 17:11     ` Jorge A. Alfaro-Murillo
2015-04-21 21:08       ` Nikolaus Rath
2015-04-21 23:03         ` How to match TODO items not SCHEDULED or DEADLINE'd (was: Sparse tree for undated TODOs, or hierachical agenda?) Nikolaus Rath
2015-04-22 14:03           ` How to match TODO items not SCHEDULED or DEADLINE'd Jorge A. Alfaro-Murillo
2015-04-22 15:49             ` Nicolas Goaziou
2015-04-22 16:10               ` Jorge A. Alfaro-Murillo
2015-04-21 23:08         ` Sparse tree for undated TODOs, or hierachical agenda? Nikolaus Rath
2015-04-22 13:52         ` Jorge A. Alfaro-Murillo

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=87fv7yhzx3.fsf@vostro.rath.org \
    --to=nikolaus@rath.org \
    --cc=emacs-orgmode@gnu.org \
    /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).