From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Dimming ancestors in the agenda (relevant to indenting nested TODOs in agenda views)
Date: Wed, 24 Aug 2011 15:07:17 +0800 [thread overview]
Message-ID: <87mxez8eze.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAJcAo8sZL0A_f1G-EyrBg=uQhhgQV1ENSEHGwJpV=6yyqqyxVA@mail.gmail.com
On Wed, Aug 24 2011, Samuel Wales wrote:
> Here is a different solution. It is from my notes from long ago.
>
> To me, one issue with indenting is that you expect the previous line
> to be a direct parent, analogously with the outline. This conflicts
> with sorting and non-child descendents.
>
> If you sort, you can't take advantage of the feature and have it look
> right. If it's not a direct child, you can't take advantage of it
> either because you either confusingly indent too much or modify the
> semantics. Also, indenting interferes with putting as much
> information on the line as possible. Those with large fonts or small
> (e.g. mobile) displays value the real estate.
>
> ===
>
> Here is an alternate, which might or might not satisfy the OP's needs
> tangentially, but might spark discussion in either case.
>
> One feature I have long wanted, but have not been able to implement,
> is to dim (or color) any agenda entry that has a descendant in the
> same agenda view.
>
> ===
>
> This is a completely different thing from dimming blocked
> tasks, because it only looks at other tasks in the same
> view, and doesn't care about todo keywords.
>
> The pseudocode is this:
>
> loop for i in all headlines in agenda (even a combined agenda)
> if i has an ancestor in agenda, dim that ancestor
>
This is interesting, and certainly could be a potential display option.
It still sort of begs the question of how to get level and/or
child/ancestor information attached to the collected TODOs as they're
being produced for the agenda views.
I'm starting with the easiest use-case: attaching a "level" text
property to each TODO. I'm trying to do this for TODOs produced by
`org-todo-list' (used by the ?t and ?T dispatch commands) and
`org-tags-view' (used by the ?m and ?M dispatchers). The former employs
`org-agenda-get-day-entries' and then `org-agenda-get-todos' to find its
TODOs, the latter uses `org-scan-tags'.
I've put code into both `org-agenda-get-todos' and `org-scan-tags' that
attaches a "level" property to outgoing TODOs, and so far that's working
okay. A smarter thing to do would probably be attaching a "parent"
property that points to the parent headline. Different display options
could then use that information to munge the agenda display in different
ways: dimming, indenting, prefixing a path, etc.
Anyway, I'm just thinking out loud here! If the org gurus have any
pointers or warnings, that would be appreciated…
Eric
next prev parent reply other threads:[~2011-08-24 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 18:40 Dimming ancestors in the agenda (relevant to indenting nested TODOs in agenda views) Samuel Wales
2011-08-24 7:07 ` Eric Abrahamsen [this message]
2011-09-10 21:02 ` Samuel Wales
2011-09-12 9:30 ` Eric Abrahamsen
2011-09-24 13:51 ` Eric Abrahamsen
2011-09-24 13:55 ` Eric Abrahamsen
2011-09-24 23:54 ` Samuel Wales
2011-09-25 3:59 ` Eric Abrahamsen
2011-09-25 4:55 ` Samuel Wales
2011-09-25 5:52 ` Eric Abrahamsen
2012-04-23 23:10 ` Bastien
2012-04-25 6:25 ` Eric Abrahamsen
2012-04-26 13:44 ` Bastien
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=87mxez8eze.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).