From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Bug: Special property ITEM without stars [9.1.14] Date: Fri, 14 Dec 2018 09:36:07 -0500 Message-ID: <87imzwyy3s.fsf@norang.ca> References: <87k1kqjk1q.fsf@nicolasgoaziou.fr> <87r2eu90zm.fsf@nicolasgoaziou.fr> <87pnu6itli.fsf@nicolasgoaziou.fr> <87mup9zek1.fsf@norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36343) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gXoZu-0005UD-EB for emacs-orgmode@gnu.org; Fri, 14 Dec 2018 09:36:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gXoZq-0007Mf-Qg for emacs-orgmode@gnu.org; Fri, 14 Dec 2018 09:36:34 -0500 Received: from outbound3d.ore.mailhop.org ([54.186.57.195]:46311) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gXoZn-00079S-36 for emacs-orgmode@gnu.org; Fri, 14 Dec 2018 09:36:28 -0500 In-Reply-To: (Allen Li's message of "Thu, 13 Dec 2018 16:52:56 -0800") 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" To: Allen Li Cc: Org Mode List Allen Li writes: > On Thu, Dec 13, 2018 at 6:28 AM Bernt Hansen wrote: >> >> Allen Li writes: >> >> > On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou wrote: >> >> >> >> This is not satisfying, actually. If every item has a single asterisk, >> >> you miss hierarchy between headlines in the same tree. >> > >> > I don't know what you mean. Hierarchy is not displayed normally in >> > agenda view anyway, I don't know why displaying it in agenda column >> > view via the ITEM property is desirable? >> > >> >> I use hierarchy in my custom agenda view everyday. Please do not remove >> this feature. > > Apparently I'm missing something. How are you using hierarchy in an > agenda view? Agenda views are flat, e.g.: > > tasks: TODO [#A] Some task > tasks: TODO [#A] Some task > tasks: TODO [#A] Some task > tasks: TODO Some task > tasks: TODO Some task > tasks: TODO Some task > > If I remember correctly, the reason they're flat is that it generally > doesn't make sense to show the hierarchy because it won't make any > sense. For example, the following: > > * TODO Project A > ** Some project A notes > * Project B > ** TODO Some task for B > > would have this hierarchy in an agenda view if we hypothetically displayed it: > > tasks: * TODO Project A > tasks: ** TODO Some task for B > > which I think is confusing at best (but I can believe is useful for > some work flows if you're careful). > In my custom agenda view for Projects I set (org-tags-match-list-sublevels 'indented) (Tags have been removed for clarity) Projects Rxxxx: TODO Rxxxx Some Release Rxxxx: .TODO Some Project Rxxxx: ..TODO Some SubProject Rxxxx: ...NEXT Some Task Rxxxx: .TODO Another Project Rxxxx: ..TODO Another Subproject Rxxxx: ...TODO Another Subproject Rxxxx: ....NEXT Another Task Rxxxx: ..TODO Another Subproject [2/6] which matches my actual tasks in Development.org #+TITLE: Development * TODO Rxxxx Some Release ** TODO Some Project *** TODO Some Subproject **** NEXT Some Task ** TODO Another Project *** TODO Another Subproject **** TODO Another Subproject ***** NEXT Another Task *** TODO Another Subproject [2/6] ... Regards, Bernt