From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tassilo Horn Subject: Re: higher level headline as category Date: Fri, 08 May 2009 14:40:13 +0200 Message-ID: <87r5yzzs2a.fsf@thinkpad.tsdh.de> References: <938fae2d0905080406r2207f925q49a735e5b9f1a483@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M2PNW-0007u3-OO for emacs-orgmode@gnu.org; Fri, 08 May 2009 08:40:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M2PNS-0007sA-5K for emacs-orgmode@gnu.org; Fri, 08 May 2009 08:40:38 -0400 Received: from [199.232.76.173] (port=51836 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M2PNS-0007s4-1J for emacs-orgmode@gnu.org; Fri, 08 May 2009 08:40:34 -0400 Received: from main.gmane.org ([80.91.229.2]:41068 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M2PNR-0004av-Hn for emacs-orgmode@gnu.org; Fri, 08 May 2009 08:40:33 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1M2PNH-0004BD-QI for emacs-orgmode@gnu.org; Fri, 08 May 2009 12:40:23 +0000 Received: from p54af17b6.dip0.t-ipconnect.de ([84.175.23.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 08 May 2009 12:40:23 +0000 Received: from tassilo by p54af17b6.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 08 May 2009 12:40:23 +0000 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Eraldo Helal writes: > In my custom agenda: Is there a way to get the higher(by1level) > *headline as prefix*? No, not that I know of. But you can use the :CATEGORY: property. > test1.org: > > * headline1 :PROPERTIES: :CATEGORY: headline1 :END: > ** TODO headline2 > ** TODO headline3 > > test2.org: Well, here it's a bit inconvenient. > * headline4 :PROPERTIES: :CATEGORY: headline4 :END: > ** headline5 :PROPERTIES: :CATEGORY: headline5 :END: > *** TODO headline 6 > ** TODO headline 7 :tag1: > > agenda: > > headline1 TODO headline2 > headline1 TODO headline3 > headline4 TODO headline7 :tag1: > headline5 TODO headline6 I think that should give the desired results, but for deeper structures always adding a property is really inconvenient. Once I used properties quite intensively, but after a while I switched to using tags and categories only for distinguishing private from work related things (and there the categories are the org file names). Bye, Tassilo