From: Samuel Wales <email@example.com> To: Eric Abrahamsen <firstname.lastname@example.org> Cc: email@example.com Subject: Dimming ancestors in the agenda (relevant to indenting nested TODOs in agenda views) Date: Tue, 23 Aug 2011 11:40:30 -0700 [thread overview] Message-ID: <CAJcAo8sZL0A_f1G-EyrBg=uQhhgQV1ENSEHGwJpV=6yyqqyxVA@mail.gmail.com> (raw) 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 Motivation is that sometimes I mark a task as important (or any other tag), and mark its child as important. When I look at the agenda view for important items without inheritance, I am less interested in the parent because there is something important in a descendent. But when B is done, I am interested in A again. I don't want to manipulate tags. I just want to have both there all the time in the agenda, but one dimmed. * deal with company A :important: * call B at company A :important: * call C === Hope this idea helps the OP's indenting need or similar ones. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com I support the Whittemore-Peterson Institute (WPI) === Bigotry against people with serious diseases is still bigotry.
next reply other threads:[~2011-08-23 18:40 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-23 18:40 Samuel Wales [this message] 2011-08-24 7:07 ` Eric Abrahamsen 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='CAJcAo8sZL0A_f1G-EyrBg=uQhhgQV1ENSEHGwJpV=6yyqqyxVA@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Dimming ancestors in the agenda (relevant to indenting nested TODOs in agenda views)' \ /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
Code repositories for project(s) associated with this 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).