Detlef Steuer <[email protected]> writes:
> Am Fri, 03 Apr 2015 17:59:16 +0200
> schrieb Nicolas Goaziou <[email protected]>:
>
>> This is to be expected. You can set :CATEGORY: node property in
>> subtrees if needed.
>
> So this beheaviour changed at some point in the past?
This behaviour was long deprecated. Starting from Org 5.14 (released in
2008), the manual stated
@cindex #+CATEGORY
The category is a broad label assigned to each agenda item. By default,
the category is simply derived from the file name, but you can also
specify it with a special line in the buffer, like this@footnote{For
backward compatibility, the following also works: if there are several
such lines in a file, each specifies the category for the text below it.
The first category also applies to any text before the first CATEGORY
line. However, using this method is @emph{strongly} deprecated as it is
incompatible with the outline structure of the document. The correct
method for setting multiple categories in a buffer is using a
property.}:
I only removed the backward compatibility recently. I dropped a note in
ORG-NEWS.
> To be sure:
>
> I have a file (modulo scheduling information)
>
> * Line1
> #+CATEGORY: one
> ** TODO very important
>
> * Line2
> #+CATEGORY: two
> ** TODO more stuff
>
> It is expected to see both TODOs in an agenda as:
>
> two: very important
> two: more stuff
Yes, it is.
This should be
* Line1
:PROPERTIES:
:CATEGORY: one
:END:
** TODO very important
* Line2
:PROPERTIES:
:CATEGORY: two
:END:
** TODO more stuff
Regards,
