emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Tim O'Callaghan" <tim.ocallaghan@gmail.com>
To: Adam Spiers <orgmode@adamspiers.org>,
	org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: property searches for #+CATEGORY
Date: Wed, 7 Nov 2007 14:23:12 +0100	[thread overview]
Message-ID: <3d6808890711070523u50bd8bbp963960978171e132@mail.gmail.com> (raw)
In-Reply-To: <20071107111730.GH13544@atlantic.linksys.moosehall>

On 07/11/2007, Adam Spiers <orgmode@adamspiers.org> wrote:
> I have several personal .org files, and several work-related ones too.
> In each personal file, I have a line:
>
>   #+CATEGORY: personal
>
> and in each work-related file, I have a line:
>
>   #+CATEGORY: work
>
> I would like to be able to bind agenda custom commands to do tag
> searches which are narrowed to one of these categories, e.g. "show me
> all personal priority #A tasks".  Such a search needs to span *all*
> agenda files, therefore the standard per-buffer narrowing provided by
> the '<' binding in the *Agenda Commands* buffer is insufficient.
>
> Would it make sense to include CATEGORY as a special property?  After
> all, pretty much all other per-task meta-data ("TODO", "PRIORITY"
> etc.) are already available via the property interface, and this way,
> I could easily achieve what I need with tag searches such as
>
>   CATEGORY="personal"+PRIORITY="A"
>
> Thanks!
>

It would seem to me that this is exactly what tags does.
You could move everything down a level and use tag inheritance:
* personal stuff :personal:
* work stuff :work:

Tim.

  parent reply	other threads:[~2007-11-07 13:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 11:17 property searches for #+CATEGORY Adam Spiers
2007-11-07 12:49 ` Bastien
2007-11-07 12:15   ` Adam Spiers
2007-11-07 13:23 ` Tim O'Callaghan [this message]
2007-11-07 13:34   ` Adam Spiers
2007-11-07 13:59     ` Tim O'Callaghan
2007-11-07 14:28       ` Adam Spiers
2007-11-07 14:52         ` Tim O'Callaghan
2007-11-07 16:35           ` Adam Spiers
2007-11-07 16:15       ` Carsten Dominik
2007-11-07 18:07         ` Adam Spiers
2007-11-08  4:55         ` Bastien
2007-11-08  8:54           ` Carsten Dominik
2007-11-07 14:49     ` Bastien
2007-11-07 14:32       ` Adam Spiers
2007-11-07 14:15 ` Bastien
2007-11-07 13:52   ` Adam Spiers
2007-11-07 17:16     ` Bastien
2007-11-07 17:23       ` Adam Spiers
2007-11-08  4:42         ` Bastien
2007-11-07 16:20   ` Carsten Dominik
2007-11-08  0:04     ` Adam Spiers
  -- strict thread matches above, loose matches on Subject: below --
2008-12-07 23:35 Mario E. Munich
2008-12-08 16:40 ` Carsten Dominik
2008-12-09  0:33   ` Mario E. Munich
2008-12-09  1:41     ` Matthew Lundin
2008-12-09  6:51       ` Mario E. Munich
2008-12-07 23:39 Mario E. Munich

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=3d6808890711070523u50bd8bbp963960978171e132@mail.gmail.com \
    --to=tim.ocallaghan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@adamspiers.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).