From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Standard agenda views don't show file name after update (replaced by "???:") Date: Fri, 03 Apr 2015 21:12:30 +0200 Message-ID: <878ue9yqjl.fsf@nicolasgoaziou.fr> References: <87r3s3wpd1.fsf@nicolasgoaziou.fr> <20150403122104.421780f9@linux-w3xx.localdomain> <87h9sxyzhn.fsf@nicolasgoaziou.fr> <20150403185017.0f12f9bb@linux-w3xx.localdomain> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34260) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ye6zu-0003UT-AQ for emacs-orgmode@gnu.org; Fri, 03 Apr 2015 15:11:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ye6zr-00025M-31 for emacs-orgmode@gnu.org; Fri, 03 Apr 2015 15:11:18 -0400 Received: from relay6-d.mail.gandi.net ([2001:4b98:c:538::198]:33093) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ye6zq-00025E-Sx for emacs-orgmode@gnu.org; Fri, 03 Apr 2015 15:11:15 -0400 In-Reply-To: <20150403185017.0f12f9bb@linux-w3xx.localdomain> (Detlef Steuer's message of "Fri, 3 Apr 2015 18:50:17 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Detlef Steuer Cc: emacs-orgmode@gnu.org Detlef Steuer writes: > Am Fri, 03 Apr 2015 17:59:16 +0200 > schrieb Nicolas Goaziou : > >> 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,