From: Carsten Dominik <dominik@science.uva.nl>
To: Paul Mead <paul.d.mead@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Stuck projects not ignoring inherited tags
Date: Thu, 19 Feb 2009 16:41:33 +0100 [thread overview]
Message-ID: <C333987A-C8DF-43EE-B879-19BBE9863CFD@uva.nl> (raw)
In-Reply-To: <u63j6sara.fsf@gmail.com>
On Feb 19, 2009, at 4:32 PM, Paul Mead wrote:
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>>
>> However, you can do this in the initial match. Make it
>>
>> "+LEVEL>=2-someday/-DONE"
>>
>> note that the level is >=2, not =2 anymore.
> Excellent, that did the trick, thanks. Can I exclude more tags in this
> way, or does the syntax change?
Tags matches in general are explained here
http://orgmode.org/manual/Tag-searches.html#Tag-searches
and here
http://orgmode.org/manual/Property-searches.html#Property-searches
>
>
>>
>> The docstring of that variable does describe what its value
>> needs to look like. Is that not extensive enough?
>
> I'm assuming you mean the text available using M-x
> describe-variable. I'm slowly getting to grips with some of this,
> but my
> elisp knowledge is minimal.
>
> The numbered list of items describes the lists well but doesn't give
> any
> illustration of how for instance the tags/todo matcher string works.
> I'd
> never have guessed that I could use -someday/-DONE in that string
> without your pointing it out.
The manual has a section about stuck projects, did you read that?
http://orgmode.org/manual/Stuck-projects.html#Stuck-projects
- Carsten
next prev parent reply other threads:[~2009-02-19 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 15:29 Stuck projects not ignoring inherited tags Paul Mead
2009-02-19 14:59 ` Carsten Dominik
2009-02-19 15:32 ` Paul Mead
2009-02-19 15:41 ` Carsten Dominik [this message]
2009-02-19 17:52 ` Paul Mead
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=C333987A-C8DF-43EE-B879-19BBE9863CFD@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=paul.d.mead@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).