From: Jost Burkardt <jost.burkardt@web.de>
To: Sven Bretfeld <sven.bretfeld@gmx.ch>
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: CATEGORY in different levels
Date: Thu, 07 Feb 2008 00:15:00 +0100 [thread overview]
Message-ID: <87ejbp7k3v.fsf@web.de> (raw)
In-Reply-To: <87odatlnds.fsf@kamaloka.dhatu> (Sven Bretfeld's message of "Wed, 06 Feb 2008 23:40:31 +0100")
Hi Sven,
Sven Bretfeld <sven.bretfeld@gmx.ch> writes:
> Hi Carsten
>
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> Properties give much more consistent results. The :CATEGORY: property
>> applies to the entry headline above it, and to the entire tree below
>> it (unless locally overwritten by another property).
>
> Hm. Definitely not working. I made it quite secure taking your file
> below and erased every configuration except the pure (require
> 'org-install).
Sorry to correct you, but the result is correct. As Carsten said:
The :CATEGORY: property applies to the entry headline _above_ it, and to
the entire tree below it
So in your example
>> * Teaching
>> :PROPERTIES:
>> :CATEGORY: Teaching
>> :END:
>> ** Sanskrit I (WS08) :PROJECT:
>> :PROPERTIES:
>> :CATEGORY: Sanscrit I
>> :END:
the ":CATEGORY: Sanscrit I" applies to the entry _above_, i.e.
** Sanskrit I (WS08)
and the ":CATEGORY: Teaching" is overridden. The TODO
entries in your file are _below_ ":CATEGORY: Sanscrit I"
so they will show up fine.
Think of the PROPERTIES as an attribute of the entry above.
--
Jost
next prev parent reply other threads:[~2008-02-06 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 0:10 CATEGORY in different levels Sven Bretfeld
2008-02-06 1:47 ` Bernt Hansen
2008-02-06 8:44 ` Sven Bretfeld
2008-02-06 10:02 ` Sven Bretfeld
2008-02-06 13:45 ` Bernt Hansen
2008-02-06 15:43 ` Carsten Dominik
2008-02-06 22:40 ` Sven Bretfeld
2008-02-06 23:15 ` Jost Burkardt [this message]
2008-02-06 23:31 ` Sven Bretfeld
2008-02-07 7:32 ` Carsten Dominik
2008-02-24 20:39 ` Sven Bretfeld
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=87ejbp7k3v.fsf@web.de \
--to=jost.burkardt@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=sven.bretfeld@gmx.ch \
/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).