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 15:52:55 +0100 [thread overview]
Message-ID: <3d6808890711070652l68d51190y2b4b735543cded7c@mail.gmail.com> (raw)
In-Reply-To: <20071107142805.GN13544@atlantic.linksys.moosehall>
On 07/11/2007, Adam Spiers <orgmode@adamspiers.org> wrote:
> On Wed, Nov 07, 2007 at 02:59:35PM +0100, 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:
> > > > 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.
>
> Same here. I used tags for a lot more than GTD contexts, e.g. also
> for a rough ETC and to group them by areas of responsibility.
> (N.B. Sometimes a task can be motivated by multiple areas of
> responsibility, so subheadings aren't good enough.)
>
> > How about adding the context to the tag table with a prefix character, say #?
>
> I don't follow you, sorry. Perhaps I should state explicitly that my
> need to distinguish between 'work' and 'personal' categories has
> nothing to do with my use of GTD contexts. I can (and do very often)
> work from home, and I also occasionally(!) do personal tasks from the
> office.
>
My point with the taxonomy is that Categories especially 'personal'
and 'work' can be thought of as Meta Contexts (i wanted to say
Meta-TAGS, but that might get confusing). So contexts that are
arbitrary but are used to group many actual physical contexts (TAGS)
of todo nodes.
The '#' was the thought that if you treat Categories as a type of tag,
then you could add them to the tag search mechanism. To avoid
collision, such as work - the physical context and work, the category,
prefix them with a meta-character such as # which cannot normally be
in a tag name.
So a categorised tag-todo search might be:
"#work+work+email/TODO"
Tim.
next prev parent reply other threads:[~2007-11-07 14:53 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 [this message]
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=3d6808890711070652l68d51190y2b4b735543cded7c@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).