From: Bernt Hansen <bernt@norang.ca>
To: subopt@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Is there an alternate means of defining categories?
Date: Wed, 26 Mar 2008 19:12:19 -0400 [thread overview]
Message-ID: <87fxudf5bg.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <20080326222200.GB20809@austin.rr.com> (subopt@gmail.com's message of "Wed\, 26 Mar 2008 17\:22\:00 -0500")
subopt@gmail.com writes:
> I'm looking for a way to define categories, aside from using the
> '#+CATEGORY: Whatever' method. I'd like to keep all the comments and
> other visual clutter out of the actual data portions of my
> files. Using the 'odd' and 'hide leading stars' has helped a lot. If i
> could just move the category definitions elsewhere, and still have
> multiple categores per file, then i'd be free and clear of all my line
> noise.
I don't use #+CATEGORY: anymore. I use properties. I define the top
level task with a specific category and all subtasks inherit the same
property (and therefore are in the same category unless otherwise
specified)
The following are from my todo.org file:
* Tasks :newtask:
:PROPERTIES:
:CATEGORY: Tasks
:ARCHIVE: %s_archive::* Miscellaneous
:END:
* Anniversaries and Holidays :notaproject:
*** Birthdays
:PROPERTIES:
:CATEGORY: Birthday
:END:
* Appointments :notaproject:
:PROPERTIES:
:CATEGORY: Appt
:ARCHIVE: %s_archive::* Appointments
:END:
* Basement :@home:
:PROPERTIES:
:CATEGORY: Basement
:ARCHIVE: %s_archive::* Basement
:END:
* Health :@home:
:PROPERTIES:
:CATEGORY: Health
:ARCHIVE: %s_archive::* Health
:END:
The :PROPERTIES:...:END: is normally folded and is not exported (if you
export your org files)
HTH,
Bernt
prev parent reply other threads:[~2008-03-26 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 22:22 Is there an alternate means of defining categories? subopt
2008-03-26 23:12 ` Bernt Hansen [this message]
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=87fxudf5bg.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=subopt@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.