Hi Eric,
Eric Abrahamsen e...@ericabrahamsen.net writes:
if I revisited nested todos, I would just write it on top of
org-element, rather than the existing org-agenda code. Eventually!
Great. Let's keep the future open then :)
--
Bastien
On Tue, Apr 24 2012, Bastien wrote:
Hi Eric,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Okay, here's an attempt at indicating nested todos in the todo agenda
view.
Sorry to come back to this old patch -- I tried it (I had to rework it
to apply it against current git master) and it
Hi Eric,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Okay, here's an attempt at indicating nested todos in the todo agenda
view.
Sorry to come back to this old patch -- I tried it (I had to rework it
to apply it against current git master) and it doesn't work, some calls
go beyond
Okay, here's an attempt at indicating nested todos in the todo agenda
view.
The more I futzed with comparing consecutive TODOs the hackier it
seemed, so I went with something more fundamental. Right now I think
this is a bigger solution than the problem warranted, but it might also
open the way
On Sat, Sep 24 2011, Eric Abrahamsen wrote:
Okay, here's an attempt at indicating nested todos in the todo agenda
view.
That might not have been the most useful way to attach the diff, sorry.
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index b1fa5f5..417566d 100644
---
Hi Eric,
Looks like you put a lot of work into this.
Some comments:
On 2011-09-24, Eric Abrahamsen e...@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
On Sun, Sep 25 2011, Samuel Wales wrote:
Hi Eric,
Looks like you put a lot of work into this.
Not that much work, in the end -- most of the effort was figuring out
how the existing code works.
Some comments:
On 2011-09-24, Eric Abrahamsen e...@ericabrahamsen.net wrote:
along the way. One
On 2011-09-24, Eric Abrahamsen e...@ericabrahamsen.net wrote:
into trees -- how you format what is wide open. To be honest I'm not
sure how one would go about dimming a TODO (I don't think font
properties support something like reduce the opacity of the current
foreground color by 50%), but
On Sun, Sep 25 2011, Samuel Wales wrote:
[...]
My goal is simple: go through entries in the already-built agenda and
dim anything that has a descendent in the same agenda.
Hierarchical sorting is for the future. And it is undesirable if you
do not have the horizontal real estate to
On Sun, Sep 11 2011, Samuel Wales wrote:
Eric,
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
This might or might not solve all your needs, but one option for
finding ancestors is to simply grab the olpath
Eric,
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
This might or might not solve all your needs, but one option for
finding ancestors is to simply grab the olpath for each agenda line.
Then you can compare
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
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
13 matches
Mail list logo
