From: Carsten Dominik <dominik@science.uva.nl>
To: Rainer Stengele <rainer.stengele@diplan.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: file level categories
Date: Fri, 7 Mar 2008 10:45:26 +0100 [thread overview]
Message-ID: <D25AC299-CA5E-49FB-BF3E-8B180F2DDF2B@science.uva.nl> (raw)
In-Reply-To: <47D0FCD7.8070602@diplan.de>
On Mar 7, 2008, at 9:29 AM, Rainer Stengele wrote:
> Eddward DeVilla schrieb:
>> On Thu, Mar 6, 2008 at 3:13 PM, Joel J. Adamson <jadamson@partners.org
>> > wrote:
>>
>>> I'm a little confused. Forgetting for the moment what the OP
>>> wants to
>>> accomplish, if I have multiple
>>>
>>> #+CATEGORY
>>>
>>> lines in a buffer, each one shows up in my agenda indexed by the
>>> category immediately preceding it. Is there some other way *I
>>> should*
>>> do this?
>>
>> The #+CATEGORY is more of a legacy thing now. Unless you are like me
>> and try to have one category per file, you should use the category
>> property in the property drawer for an item.
>>
>> Edd
>>
>>
>> _______________________________________________
>> 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
>>
>
> you mean if I have 5 blocks of items, each belonging to another
> CATEGORY
> I have to add a CATEGORY drawer to each and every item?
You dont have to. However, the Use of #+CATEGORY has its problems.
In particular,
in an outline, there is no such place as "between entries or trees".
Therefore,
from the logical structure of the file, #+CATEGORY is always part of
the previous
entry. It is therefore confusing to have it set the category for the
following
stuff.
If you only have top-level entries, putting category properties can be
annoying.
However, CATEGORY is trated as a property with in inheritance. So in
* HOME tasks
:PROPERTIES:
:CATEGORY: home
:END:
** task 1
** task 2
both task 1 and task 2 have category "home".
Anyway, use of multiple #+CATEGORY lines will stay in org-mode for the
foreseeable
future, but I will never use it.
HTH
- Carsten
>
>
> I am now working ok with #+CATEGORY at the beginning of each big
> section.
>
> rainer
>
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2008-03-07 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 15:55 file level categories Eddward DeVilla
2008-03-06 19:23 ` Carsten Dominik
2008-03-06 21:13 ` Joel J. Adamson
2008-03-06 22:14 ` Bastien
2008-03-06 22:47 ` Eddward DeVilla
2008-03-07 8:29 ` Rainer Stengele
2008-03-07 9:45 ` Carsten Dominik [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
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=D25AC299-CA5E-49FB-BF3E-8B180F2DDF2B@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@diplan.de \
/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).