org-depend improvements: TRIGGER in Combination With Set SCHEDULED

[Karl Voit <devnull@Karl-Voit.at>]

* Karl Voit <devnull@Karl-Voit.at> wrote:
> * Carsten Dominik <dominik@uva.nl> wrote:
>
>> Since ord-depend was only proof of concept, we could also think a bit more
>> broadly about what it should be able to do.  Is there specific
>> functionality it also should support, besides the TRIGGER/BLOCKER functions
>> it has right now?
>
> Oh my goodness - free wishes for org-depend? Christmas is rather
> early this year! ;-)
>
> For reference purposes: http://orgmode.org/worg/org-contrib/org-depend.html

I thought about some org-depend improvements to take it to the next
level.

Since many Org-mode users do not know or use org-depend.el, I
decided to write a blog post about it and how improvements can easy
my digital life:

        http://karl-voit.at/2016/12/18/org-depend/

Some improvements are probably solved with a few lines of Elisp code.
Unfortunately, I am very bad at coding Elisp myself and thus can't
extend Emacs the way I would love to.

For discussion purposes, I now append the improvements as separate
mailinglist emails here as well:


4 Improvement: TRIGGER in Combination With Set SCHEDULED
========================================================

  I love the `:TRIGGER:' property because I can mark headings as open
  tasks only if they can be done now. Only headings which are ready to
  be looked at do have the `TODO' keyword.

  One limitation of `org-depend.el' is that I am only to move forward
  scheduled dates to siblings and I am not able to define a different
  scheduled date.

  Assume following syntax:

  ,----
  | ** TODO Asking the client about the project
  | :PROPERTIES:
  | :TRIGGER: 2016-12-18-send-offer(TODO,2016-12-23)
  | :END:
  |
  | ** Send offer to client
  | :PROPERTIES:
  | :ID: 2016-12-18-send-offer
  | :END:
  `----

  I extended the option of the trigger property so that I added an ISO
  date to the keyword parameter.

  What I'd expect is that on finishing the first task, the heading with
  the ID `2016-12-18-send-offer' not only gets the keyword `TODO' but
  also is scheduled for 2016-12-23 as well.

  Notice that the send-offer heading is not necessarily located in the
  same sub-hierarchy as the ask-client heading. Therefore,
  sibling-operations are not the whole answer here.

  Additional to this, I'd like to have the possibility to define
  relative schedule dates as stated in [manual for the date prompt]:

   `2016-12-18-send-offer(TODO,.)'      the day when marking the asking-task as done
   `2016-12-18-send-offer(TODO,+3d)'    3 days after the scheduled date of the asking-task
   `2016-12-18-send-offer(TODO,.+3d)'   3 days from the day when marking the asking-task as done
   `2016-12-18-send-offer(TODO,mon)'    nearest Monday from the day when marking the asking-task as done
   `2016-12-18-send-offer(TODO,+2tue)'  second Tuesday from the day when marking the asking-task as done


[manual for the date prompt]
http://orgmode.org/manual/The-date_002ftime-prompt.html#The-date_002ftime-prompt

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github