From: Cameron Horsburgh <cammo@netcall.com.au>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible bug with tag inheritance
Date: Sun, 26 Apr 2009 05:14:04 +1000 [thread overview]
Message-ID: <20090425191404.GF17832@earth> (raw)
In-Reply-To: <FF3CA8F9-7497-4119-8408-79FF2F0566AD@gmail.com>
On Fri, Apr 24, 2009 at 03:54:29PM +0200, Carsten Dominik wrote:
> On Apr 24, 2009, at 12:43 PM, Cameron Horsburgh wrote:
>
>> I have customised org-stuck-projects[fn:1] to ignore entries tagged
>> with the tag `Info'. org-use-tag-inheritance is set to `t'.
>>
>> If I hit C-a # to list stuck projects I would only expect to see the
>> entry about cooking dinner listed. The `Notes' headline should be
>> ignored, as should the notes about Mary's phone number and Jenny's web
>> page, because they inherit the `Info' tag.
>>
>> In practice, the `Notes' headline is ignored as expected. However, the
>> children are listed as stuck projects.
>>
>> After all this I have realised it's probably more appropriate to use
>> properties rather than tags to do this sort of thing. Still, the
>> behaviour puzzles me a bit, so I thought it was worth asking about.
>>
>> Is this behaviour incorrect? Or am I expecting the wrong thing?
>
>
> The tags in org-stuck-projects must be present explicitly in the
> subtree, because the subtree is searched with a regula expression that
> does not know about inheritance.
I thought this might be the case. May I suggest a note be made to the
documentation of org-stuck-projects?
>
> However, you can include this into your definition of a project:
>
> (setq org-stuck-projects
> (quote ("+LEVEL=2-Info/-DONE" ("TODO" "NEXT" "NEXTACTION") nil "")))
>
> HTH
>
>
>>
>> * Footnotes
>>
>> [fn:1] I had some trouble customising this variable in the usual way,
>> because the explanation at the end of the customize buffer somehow got
>> included in the sexp recorded in my .emacs. I deleted that line, reset
>> the customize buffer and started again, but with exactly the same
>> result.
>
> There seems to be a bug in customize. Can anyone please submit a but
> report to Emacs, after verifying that this still occurs in the latest
> update of emacs 23?
>
I'll have a play with some other customized buffers and see what
happens. If it happens elsewhere I'll send a report.
--
Cameron Horsburgh
Blog: http://spiritcry.wordpress.com/
next prev parent reply other threads:[~2009-04-25 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 10:43 Possible bug with tag inheritance Cameron Horsburgh
2009-04-24 12:45 ` Bernt Hansen
2009-04-24 13:08 ` Cameron Horsburgh
2009-04-24 13:24 ` Bernt Hansen
2009-04-24 18:02 ` Cameron Horsburgh
2009-04-24 18:12 ` Bernt Hansen
2009-04-25 18:54 ` Cameron Horsburgh
2009-04-24 13:54 ` Carsten Dominik
2009-04-25 19:14 ` Cameron Horsburgh [this message]
2009-04-25 20:55 ` 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:
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=20090425191404.GF17832@earth \
--to=cammo@netcall.com.au \
--cc=carsten.dominik@gmail.com \
--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).