From: Bernt Hansen <bernt@norang.ca>
To: Allen Li <darkfeline@felesatra.moe>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Bug: Special property ITEM without stars [9.1.14]
Date: Fri, 14 Dec 2018 09:36:07 -0500 [thread overview]
Message-ID: <87imzwyy3s.fsf@norang.ca> (raw)
In-Reply-To: <CADbSrJy3j6_dYq2fiK1fHd6HrGAeQVwnd3atUsX053rL8cf0RA@mail.gmail.com> (Allen Li's message of "Thu, 13 Dec 2018 16:52:56 -0800")
Allen Li <darkfeline@felesatra.moe> writes:
> On Thu, Dec 13, 2018 at 6:28 AM Bernt Hansen <bernt@norang.ca> wrote:
>>
>> Allen Li <darkfeline@felesatra.moe> writes:
>>
>> > On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> 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
next prev parent reply other threads:[~2018-12-14 14:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 22:19 Bug: Special property ITEM without stars [9.1.14] Allen Li
2018-12-03 22:57 ` Nicolas Goaziou
2018-12-04 10:14 ` Allen Li
2018-12-04 10:19 ` Allen Li
2018-12-06 14:35 ` Nicolas Goaziou
2018-12-07 5:26 ` Allen Li
2018-12-12 16:43 ` Nicolas Goaziou
2018-12-12 22:50 ` Allen Li
2018-12-13 14:28 ` Bernt Hansen
2018-12-14 0:52 ` Allen Li
2018-12-14 13:11 ` Nicolas Goaziou
2018-12-14 14:36 ` Bernt Hansen [this message]
2018-12-14 20:58 ` Allen Li
2018-12-18 11:18 ` Nicolas Goaziou
2018-12-19 3:12 ` Allen Li
2018-12-19 14:10 ` Nicolas Goaziou
2018-12-19 19:30 ` Allen Li
2018-12-19 20:36 ` Nicolas Goaziou
2018-12-04 10:19 ` Nicolas Goaziou
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=87imzwyy3s.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=darkfeline@felesatra.moe \
--cc=emacs-orgmode@gnu.org \
/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).