From: Samuel Wales <samologist@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Dimming ancestors in the agenda (relevant to indenting nested TODOs in agenda views)
Date: Sat, 24 Sep 2011 16:54:29 -0700 [thread overview]
Message-ID: <CAJcAo8s6=myZaJWGxYdTZ=QPq=OiLKjfeyHEBHAqgrYudhjmBw@mail.gmail.com> (raw)
In-Reply-To: <87sjnmoxp0.fsf@ericabrahamsen.net>
Hi Eric,
Looks like you put a lot of work into this.
Some comments:
On 2011-09-24, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> along the way. One bonus is that each level of TODO
> subtrees gets sorted distinctly.
My goal (which might be different from yours) is as stated
in the subject header; it's merely to dim any agenda entry
that has any descendent of it anywhere in the same agenda.
There would be no other differences, so sorting would be the
same.
> (defcustom org-agenda-todo-list-sublevels t
> - "Non-nil means check also the sublevels of a TODO entry
> for TODO entries.
This looks like it only works for the agenda command(s) that
list(s) todos, not for tags, text search, or daily/weekly
agenda. Is that correct?
I reviewed the manual and
http://orgmode.org/worg/org-tutorials/advanced-searching.html#combining-metadata-and-full-text-queries
.
I've actually never understood the usefulness of the c-c a t
view, given that all todo searches (IIUC) can in principle
be implemented with a tags search and c-c a t would take
forever with a large set of agenda files. Also, I rarely
use T (and only interactively) and never use M.
So your patch would actually not be useful to me, as I
essentially don't use the todo searches.
> + "How to display TODO entries that are sublevels of a TODO entry.
> +When nil, the sublevels of a TODO entry are not returned,
> +resulting in potentially much shorter TODO lists. When t, the
This seems to allow you to dim sublevels, not ancestors. So
it is actually the opposite of this thread's subject.
Also, it seems to merge the concept of skipping sublevels
with dimming. My guess is that they should be separated.
Of course, it is your code and you know it best.
Dimming of ancestors can be done after the entire agenda is
created. So it need not be involved in the initial scanning
of the outline at all, unless that is needed for efficiency.
===
It is probable that I do not understand what your goal is,
as it is different from mine. The two goals might or might
not be advisable to implement with the same approach.
My goal is simply to dim anything in the agenda that has any
descendant that is also showing in the agenda, efficiently.
That way, if you have a project and a NEXT underneath it,
the project will be dimmed and the NEXT will not, without
any manual manipulation of metadata necessary.
Hope it helps.
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 prev parent reply other threads:[~2011-09-24 23:54 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
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 [this message]
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='CAJcAo8s6=myZaJWGxYdTZ=QPq=OiLKjfeyHEBHAqgrYudhjmBw@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).