[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] Possible bug with tag inheritance

From: Cameron Horsburgh
Subject: Re: [Orgmode] Possible bug with tag inheritance
Date: Sun, 26 Apr 2009 05:14:04 +1000
User-agent: Mutt/1.5.18 (2008-05-17)

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 "")))
>> * 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/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]