From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karl Voit Subject: Re: org-depend: dependencies between TODO entries in different files Date: Mon, 12 Dec 2016 16:17:54 +0100 Message-ID: <2016-12-12T15-59-38@devnull.Karl-Voit.at> References: <2016-08-25T14-36-57@devnull.Karl-Voit.at> <877fb429j4.fsf@saiph.selenimh> <2016-08-25T17-05-15@devnull.Karl-Voit.at> <87mvg2t8g0.fsf@artlab.createcnix.lan> <2016-12-12T12-38-45@devnull.Karl-Voit.at> Reply-To: Karl Voit Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37025) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGSMj-00020l-Mc for emacs-orgmode@gnu.org; Mon, 12 Dec 2016 10:18:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cGSMg-0001dj-FH for emacs-orgmode@gnu.org; Mon, 12 Dec 2016 10:18:09 -0500 Received: from [195.159.176.226] (port=49071 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cGSMg-0001dN-7c for emacs-orgmode@gnu.org; Mon, 12 Dec 2016 10:18:06 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cGSMZ-0000V4-7r for emacs-orgmode@gnu.org; Mon, 12 Dec 2016 16:17:59 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org * Carsten Dominik wrote: > > Dear all, Hi Carsten, > 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! ;-) OK, let's do some brain storming ... For reference purposes: http://orgmode.org/worg/org-contrib/org-depend.html > One issue to deal with is, that in different files, a different set of TODO > keywords might be active, so if a TRIGGER entry changes a TODO state, and > that entry lives in a different file, it falls onto the user to make sure > that the required state is valid in both files. >From my point of view: due to the fact that the user has to state the TRIGGER keyword manually, it is up to the user that this makes any sense. So far, nothing prevents me from typing: :TRIGGER: foo-bar(INVALIDSTATUS) > Any ides what is missing or might be useful? Well, this comes a bit unprepared (I might be able to come up with more feature possibilities to org-depend when thinking about it) but I'd say that following workflows would be nice to discuss about: Being able to specify SCHEDULED-dates *and* next status for arbitrary IDs. For example: ** NEXT Asking the client about XY :PROPERTIES: :TRIGGER: send-task(NEXT,2016-12-23) :END: ** Send XY to client :PROPERTIES: :ID: send-task :END: Well the syntax might be chosen differently. What I want to achieve is that when changing the "Asking" task to a finished state, the "Send" task gets a fixed SCHEDULED value and the status NEXT. Additional: the two tasks are not necessarily in the same file or within the same sub-hierarchy. So the «inherit scheduled date» feature via chain-siblings-scheduled does not work in most cases to me. Another one: ** NEXT Asking the client about XY SCHEDULED: <2016-12-12> :PROPERTIES: :TRIGGER: send-task(NEXT,.+3d) :END: ** Send XY to client :PROPERTIES: :ID: send-task :END: When the "Asking" task is set to a finished state, the "Send" task will be scheduled three days in the future and gets the status NEXT. The usual date-syntax applies here as well: +3d (3 days from maybe the SCHEDULED(?) date of the "Asking" task), .+3d (3 days from now), and so forth. Another one: having the possibility to define "Send" state changes that rely on the "Asking" state. For example: If I cancel the "Asking" task, the "Send" state should be cancelled as well because it makes no sense without the first one. -- 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