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

Hi Max, Max Mikhanosha writes: > At Wed, 27 Jul 2011 13:33:16 +0200, > Bastien wrote: >> >> 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 > > Done, will push on

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

At Wed, 27 Jul 2011 13:33:16 +0200, Bastien wrote: > > 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 > Done, will push once I have permissions

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

Hi Max, Max Mikhanosha writes: > Amended patch attached, changes: > > - use (eval-when-compile) with require 'cl > - changed include-done to todo-and-done-only > - Added defcustom org-depend-find-next-options for default options > which are now: from-current,todo-only,priority-up > - cleaned u

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

Hi Max, Max Mikhanosha 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 candi

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

Amended patch attached, changes: - use (eval-when-compile) with require 'cl - changed include-done to todo-and-done-only - Added defcustom org-depend-find-next-options for default options which are now: from-current,todo-only,priority-up - cleaned up documentation Also attached is updated tes

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

At Tue, 26 Jul 2011 13:48:30 +0200, Bastien wrote: > > > +;; list and then filtered and sorted according to OPTIONS > > +;;- The first sibling on the list is changed into KEYWORD state > > +;;- The sibling also gets the same TRIGGER property > > +;; "chain-siblings-scheduled", so

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

"Sebastien Vauban" writes: > Shouldn't we do that (require cl only) in our custom .emacs files > neither? ~/.emacs.el is precisely the place where you do what you want :) -- Bastien

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

Hi Bastien, Bastien wrote: >> +(require 'cl) > > This (eval-when-compile (require 'cl)) -- Emacs has a policy of > preventing (require 'cl) only... Shouldn't we do that (require cl only) in our custom .emacs files neither? I do have such for accessing functions like `push'... Best regards, Se

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

Hi Max, Max Mikhanosha writes: > org-depend TRIGGER chain-siblings(NEXT) property is hardly usable for > me, because it requires too much effort to keep items nicely sorted. > > For example if next headline is already in DONE state, chain-siblings > would still change it. I prefer to sort my ite

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

org-depend TRIGGER chain-siblings(NEXT) property is hardly usable for me, because it requires too much effort to keep items nicely sorted. For example if next headline is already in DONE state, chain-siblings would still change it. I prefer to sort my items by setting their priorities and/or effor