emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: "Daniel J. Sinder" <djsinder@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Categories in tags-TODO agendas
Date: Thu, 25 May 2006 06:01:03 +0200	[thread overview]
Message-ID: <d8af06f9f73a47d4f0912f421e4f37eb@science.uva.nl> (raw)
In-Reply-To: <4474C049.1070809@gmail.com>

Hi Daniel

On May 24, 2006, at 22:21, Daniel J. Sinder wrote:
>
> I've recently encountered one bug and one inconsistency (I'm up to
> date with 4.33).
>
> Here's the bug:  After generating the first weekly agenda and
> quitting it, subsequent tag-search agendas result in the same
> CATEGORY label on all entries regardless of the CATEGORY label on
> the file that produced the entry.  Subsequent weekly agendas still
> show the correct categories however.  (It's not obvious to me if
> there's any consistency as to *which* file's category is selected
> for the tag searches.)


I guess this should be the last file in the org-agenda-file-list?

Please try the following patch which should fix this bug, thank you for 
the report!

--- org.el.orig	Wed May 24 11:39:48 2006
+++ org.el	Thu May 25 00:00:30 2006
@@ -7596,6 +7561,8 @@
  	  (with-current-buffer buffer
  	    (unless (eq major-mode 'org-mode)
  	      (error "Agenda file %s is not in `org-mode'" file))
+	    ;; FIXME: check if adding this solves the category problem
+	    (setq org-category-table (org-get-category-table))
  	    (save-excursion
  	      (save-restriction
  		(if org-respect-restriction

>
> And the inconsistency has to do with how tag inheritance is handled
> in tag searches.  Suppose I have in one of my org files:
>   * Projects
>   ** Resolve inconsistency with org-mode tag searches :OrgMode:
>   *** TODO Post to emacs-orgmode list :Email:
>   *** TODO Write a patch for org-mode tag searches :Computer:
>
> If I do a tag query for "OrgMode" (C-c a m OrgMode), I get
>   WORK:     Resolve inconsistency with org-mode tag searches :OrgMode"
> (that is, the TODO items do not inherit the OrgMode tag).
>
> However, if I do a TODO-only tag query for "OrgMode" (C-c a M
> OrgMode), I get both sub-headlines:
>   WORK:       ..TODO Post to emacs-orgmode list         :Email:
>   WORK:       ..TODO Write patch for org-mode tag searches :Computer
>
> I think these two should behave more alike with regard to tag
> inheritance.  I personally prefer the latter approach, wherein
> inherited tags are included in the results.

Please take a look at the variable org-tags-match-list-sublevels.

- Carsten

  reply	other threads:[~2006-05-25  4:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 20:21 Categories in tags-TODO agendas Daniel J. Sinder
2006-05-25  4:01 ` Carsten Dominik [this message]
2006-05-25 17:56   ` Daniel J. Sinder

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=d8af06f9f73a47d4f0912f421e4f37eb@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=djsinder@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).