From: Carsten Dominik <carsten.dominik@gmail.com>
To: Tim O'Callaghan <tim.ocallaghan@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: property searches for #+CATEGORY
Date: Wed, 7 Nov 2007 17:15:55 +0100 [thread overview]
Message-ID: <F4EE85D7-26D6-4BC5-A882-90A7C2A34811@science.uva.nl> (raw)
In-Reply-To: <3d6808890711070559x3b24ed3djc4276fdc09d074a9@mail.gmail.com>
Thanks for an interesting discussion about the merits of properties
versus tags etc. Very illuminating.
However, I do think that Adam's initial request to make the
category available as a special property for queries in not
unreasonble. Or does anyone disagree?
I am not sure, though, if the #+CATEGORY category should be
available with `org-entry-get', because it would then be very
hard for the property API to make a difference between a value
that is intimately associated with the current entry, and a
value that might be derived by some other mechanism. So here I
differ somewhat from Adam's feeling that category is just like
TODO or a tag. It is different.
But for the search interface, to allow CATEGORY="work", I think
that would be a safe thing to do. Will be in 5.14, unless I hear
good arguments against this.
- Carsten
On 7Nov2007, at 2:59 PM, Tim O'Callaghan wrote:
> On 07/11/2007, Adam Spiers <orgmode@adamspiers.org> wrote:
>> On Wed, Nov 07, 2007 at 02:23:12PM +0100, Tim O'Callaghan wrote:
>>> 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:
>>
>> I could, but this would mean that each file would have a single
>> top-level entry, and the entire contents would be indented an extra
>> level, which I fear is a rather unattractive solution!
>>
>
> It's the technique i've been using, and yes, it is unattractive.
>
> When i thought of tags, it was not explicitly for GTD context
> specifier, it was also for adding searchable metadata to a todo node.
> I'm finding out that it gets diluted somewhat.
>
> It guess its a matter of taxonomy. Roughly i would see this as:
>
> 1. State - TODO - DO/CANCEL/DONE
> 2. Context - tags - :@home:@phone:
> 3. Date/Time - <2007-10-10>
> 4. Meta Context - Category - personal, work etc,
> 5. Meta State - Properties drawer - :EMAIL:emacs-orgmode@gnu.org
> 6. Meta DateTime - state/time logging -
>
> How about adding the context to the tag table with a prefix
> character, say #?
>
> Tim.
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2007-11-07 17:40 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F4EE85D7-26D6-4BC5-A882-90A7C2A34811@science.uva.nl \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tim.ocallaghan@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.