Re: [PATCH] New org-depend trigger for finding next highest priority/effort item

[Bastien <bzg@altern.org>]

Hi Max,

Max Mikhanosha <max@openchat.com> writes:

>> Can you give an example?
>
> * Parent
> ** TODO Item 1
> ** TODO Item 2
> ** TODO Item 3
> ** TODO Item 4
> ** NEXT Item 5 Current  (the one with TRIGGER property)
> ** TODO Item 6
> ** Item 7
> ** TODO Item 8
> ** DONE Item 9
>
> Below are example list of candidates depending on option
>
> from-top                  => 1,2,3,4,6,7,8
> from-bottom               => 8,7,6,4,3,2,1
> from-current              => 6,7,8,1,2,3,4
> from-current,no-wrap      => 6,7,8
>
> Adding todo-only will eliminate item 7 from all of above, adding
> include-done will include item 9.
>
> After inital candidate list is established as above, its sorted by priority
> or effort, then 1st item is made NEXT.

Cristal-clear, thanks!

> I grepped *.el and saw other file using it without eval-when-compile
> (it was htmlize.el i think), so I thought it was ok in contrib. 

To be clear: it *is* okay in contrib/ as files in contrib/ will not go
to Emacs core.  But the more we can avoid this the better.

> Attached is a test file you can use for all the situation that you
> asked clarification for. After testing this file I'm thinking maybe
> from-current should be a default instead of from-top. 

Yes, I also think from-current should be the default. 

Also, it would be really nice to update this tutorial on Worg and to
show how to use the new feature you introduced:

  http://orgmode.org/worg/org-contrib/org-depend.html

Thanks!

-- 
 Bastien