From: Carsten Dominik <dominik@science.uva.nl>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [help] A org agenda command
Date: Mon, 23 Apr 2007 15:24:21 +0200 [thread overview]
Message-ID: <8bbaaec901190cf1570574695f22c1fa@science.uva.nl> (raw)
In-Reply-To: <m2wt09w9yb.fsf@sl392.st-edmunds.cam.ac.uk>
On Apr 19, 2007, at 1:15, Leo wrote:
> Dear all,
>
> How can I bring up a list of "stuck" projects? Here "stuck" means all
> of
> the following:
>
> 1. No DEADLINE/SCHEDULE
> 2. No TODO Keywords
> 3. No Tag
>
> Thank you.
You need some way to tell what a project is, for example
everything with level 2 that is not DONE.
To indicate that any TODO keyword or any tag will label the
project non-stuck, you currently have to list all TODO keywords
and all TAGS in the variable `org-stuck-projects'.
So right now you'd have to do something like:
(setq org-stuck-projects
'("+LEVEL=2/-DONE" ("TODO" "NEXT" ...) ("TAG1" "TAG2" ...)))
I can see that this is unsatisfactory, so in the next version you will
be able to specify "*" as a tag or a TODO keyword to indicate that you
mean all of them. For now this will only work in the context of stuck
projects.
(setq org-stuck-projects
'("+LEVEL=2/-DONE" ("*") ("*")))
- Carsten
next prev parent reply other threads:[~2007-04-23 13:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 23:15 [help] A org agenda command Leo
2007-04-19 15:06 ` Jason F. McBrayer
2007-04-23 13:24 ` Carsten Dominik [this message]
2007-04-23 19:11 ` Carsten Dominik
2007-04-23 19:21 ` Leo
2007-04-24 8:58 ` Leo
2007-04-24 9:22 ` Leo
2007-04-24 10:18 ` Carsten Dominik
2007-04-24 10:58 ` Leo
2007-04-24 11:11 ` Leo
2007-04-24 11:38 ` Carsten Dominik
2009-02-04 9:41 ` Leo
2009-02-04 14:22 ` Carsten Dominik
2009-02-04 15:34 ` Leo
2009-02-06 7:51 ` Carsten Dominik
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=8bbaaec901190cf1570574695f22c1fa@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=sdl.web@gmail.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).