emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Categories
Date: Fri, 12 Oct 2007 18:00:37 +0100	[thread overview]
Message-ID: <87fy0gw9my.fsf@bzg.ath.cx> (raw)
In-Reply-To: <cnd4vk4bof.fsf@home.net> (Richard G. Riley's message of "Fri, 12 Oct 2007 17:04:00 +0200")

Richard G Riley <rileyrgdev@googlemail.com> writes:

> Completion doesnt work for me. Possibly this is a result of using
> icicles? You just TAB to completion?

Can you please provide more details:

What version of Org-mode?  
What did you do?  
What did you expect?
What did you get instead?

> This might seem like an incredibly naive question, but with the
> concept of "general properties", where do TAGs fit in now?

TAGs are special properties.  They are special regarding the way you
access them (C-c C-c), the way you display them (flushright) and the 
way Org can process them (with specific search/sort queries.)

But in other respect, they are just "properties" of an entry.

Hope this might help you find the best use for tags.

> I am having difficulty seeing the best way to utilise the tools and
> would appreciate some wise words of guidance here.

For me a todo line gets associated with :

| a project           | CATEGORY     |
| a process state     | TODO keyword |
| an action-type      | tags         |
| a context of action | tags         |

My setting for tags is this:

#+TAGS:      { Read(r) Write(w) Code(c) }
#+TAGS:      Mail(m) Print(p)
#+TAGS:      { @HOME(H) @LAB(L) }
#+TAGS:      { @Online(O) @Offline(F) }

The first two lines are action-types.  

The two last lines are contexts.  The conventions I use are these: 1)
the keys for action-types are lower-case, the keys for contexts are
upper-case. 2) contexts comes with a leading "@" 3) the tags for
*physical* contexts are all capitalized, while those for notional
contexts are just first-letter capitalized.

The tags that I'm more likely to use are Read, Write or Code.  

A subset of my agenda views: 

(setq org-agenda-custom-commands
      '(("r" tags-todo "Read/NEXT" nil)
	("w" tags-todo "Write/NEXT" nil)
	("R" tags-todo "Read/NEXT|TODO" nil)
	("W" tags-todo "Write/NEXT|INPROGRESS" nil)))

Then I regularily check for something to read with "r" (meaning
something to read next) or "R" (including other TODO); or I check for
things that I have to write with "w" (the things I have to write next)
or "W" (including work in progress, which is likely to take more than 
on day.)

For the "Mail" an "Print" tags,  i use the normal C-c a m key, since I
don't use them that often.  

At the beginning I worried too much about having a consistent set of
tags.  For the example above, there is some overlap between Mail Write
and Code.  But you don't need to worry about that.  Just use the tags,
and progressively you will be able to get rid of useless one.

HTH,

-- 
Bastien

  reply	other threads:[~2007-10-12 16:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 23:05 Categories Richard G Riley
2007-10-12  3:16 ` Categories Eddward DeVilla
2007-10-12  9:00   ` Categories Richard G Riley
2007-10-12 13:31     ` Categories Bastien
     [not found]       ` <fgy7e85vf3.fsf@home.net>
2007-10-12 14:56         ` Categories Bastien
2007-10-12 14:12           ` Categories Richard G Riley
2007-10-12 14:27             ` Categories Carsten Dominik
2007-10-12 15:04               ` Categories Richard G Riley
2007-10-12 17:00                 ` Bastien [this message]
     [not found]                   ` <qfr6k0b8f8.fsf@home.net>
     [not found]                     ` <87bqb4uri3.fsf@bzg.ath.cx>
     [not found]                       ` <ml641cb5wj.fsf@home.net>
     [not found]                         ` <87r6k0tboe.fsf@bzg.ath.cx>
     [not found]                           ` <0sprzk9pcu.fsf@home.net>
     [not found]                             ` <87641cdniz.fsf@bzg.ath.cx>
     [not found]                               ` <uzk5prdwxm.fsf@home.net>
     [not found]                                 ` <87tzovjeer.fsf@bzg.ath.cx>
     [not found]                                   ` <13k5prcg2a.fsf@home.net>
     [not found]                                     ` <87bqb3jcsm.fsf@bzg.ath.cx>
     [not found]                                       ` <77zlykith7.fsf@home.net>
2007-10-15 11:32                                         ` Categories Bastien
     [not found]                   ` <jnr6jwtk1o.fsf@home.net>
2007-10-15 17:54                     ` Categories Bastien
     [not found]                       ` <t1lka4thoz.fsf@home.net>
2007-10-15 18:38                         ` Categories Bastien
     [not found]                           ` <jbhcksjmnx.fsf@home.net>
2007-10-15 18:57                             ` Categories Bastien
     [not found]                               ` <2yd4vgdyxe.fsf@home.net>
2007-10-15 19:24                                 ` Categories Bastien
2007-10-12 17:07                 ` Categories Carsten Dominik
2007-10-12 17:20                   ` Categories Richard G Riley
2007-10-12 18:20                     ` Categories Carsten Dominik
2007-10-13 12:22                       ` Categories Richard G Riley
2007-10-14  6:14                         ` Categories Carsten Dominik

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=87fy0gw9my.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --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).