emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Cameron Horsburgh <cammo@netcall.com.au>
To: emacs-orgmode@gnu.org
Subject: Possible bug with tag inheritance
Date: Fri, 24 Apr 2009 20:43:35 +1000	[thread overview]
Message-ID: <20090424104335.GA17832@earth> (raw)

Hi folks,

Today I stumbled across an instance where tag inheritance doesn't seem
to work as I expected it to.

I'm using GNU Emacs 23.0.92.1 (i486-pc-linux-gnu, GTK+ Version 2.14.7)
of 2009-04-12 on elegiac, modified by Debian, and Org-mode version
6.26trans.

Let's say I have an org file that records all the information for a
particular part of my life. Different parts of the file record
meetings, track projects and record notes and other
information. Here's what it might look like:



* Meetings
** Lunch with John						 :Restaurant:
   <2009-04-27 Mon 12:30>
** Meeting with Fred						     :Office:
   <2009-04-27 Mon 13:00>
* Projects
** Find Higgs Boson						 :Laboratory:
   DEADLINE: <2009-04-27 Mon>
** Achieve World domination				  :Office:Laboratory:
   SCHEDULED: <2009-04-28 Tue>
** Cook dinner							    :Kitchen:
* Notes								       :Info:
** Mary's phone numbers
   - 1234-5678
   - 0412-345-678
** Jenny's web page
   - [[http://www.somewebpage.com][Jenny's web page]]

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?

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


-- 

Cameron Horsburgh

Blog: http://spiritcry.wordpress.com/

             reply	other threads:[~2009-04-24 10:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 10:43 Cameron Horsburgh [this message]
2009-04-24 12:45 ` Possible bug with tag inheritance 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
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=20090424104335.GA17832@earth \
    --to=cammo@netcall.com.au \
    --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).