emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Filtering Agenda View
Date: Thu, 6 Sep 2012 16:27:39 +0000 (UTC)	[thread overview]
Message-ID: <87vcfr6s8a.fsf@mean.albasani.net> (raw)
In-Reply-To: CAFdBzEpncc4ni+U7P1s_5qYc3OLCYuVJ74nKo2CV1N3JVcZr+w@mail.gmail.com

Hi Ken,

Ken Mankoff <mankoff@gmail.com> writes:

> I tried setting the regexp to "\ WAITING\ " but that did not fix it.
> How can I improve the regexp, or is there a better way to show TODO
> items that are TODO, STARTED, WHATEVER, but not WAITING (or not

,----[ (describe-function 'org-agenda-skip-if) ]
| (org-agenda-skip-if SUBTREE CONDITIONS)
| [...]
| CONDITIONS is a list of symbols, boolean OR is used to combine the results
| from different tests.  Valid conditions are:
| scheduled     Check if there is a scheduled cookie
| notscheduled  Check if there is no scheduled cookie
| deadline      Check if there is a deadline
| notdeadline   Check if there is no deadline
| timestamp     Check if there is a timestamp (also deadline or scheduled)
| nottimestamp  Check if there is no timestamp (also deadline or scheduled)
| regexp        Check if regexp matches
| notregexp     Check if regexp does not match.
> todo          Check if TODO keyword matches
| nottodo       Check if TODO keyword does not match
| `todo' and `nottodo' accept as an argument a list of todo
| keywords, which may include "*" to match any todo keyword.
>     (org-agenda-skip-entry-if 'todo '("TODO" "WAITING"))
| would skip all entries with "TODO" or "WAITING" keywords.
| Instead of a list, a keyword class may be given.  For example:
|     (org-agenda-skip-entry-if 'nottodo 'done)

Does that help?


  reply	other threads:[~2012-09-06 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 18:50 Filtering Agenda View Ken Mankoff
2012-09-06 16:27 ` Memnon Anon [this message]
2012-09-08 15:22   ` Ken Mankoff
2012-09-09 12:04 ` Bernt Hansen
2012-09-10  0:18   ` Bernt Hansen

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:

  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=87vcfr6s8a.fsf@mean.albasani.net \
    --to=gegendosenfleisch@googlemail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).