From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christophe Schockaert Subject: Re: org-depend: dependencies between TODO entries in different files Date: Mon, 12 Dec 2016 23:23:49 +0100 Message-ID: <874m284wi2.fsf@artlab.createcnix.lan> 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> <2016-12-12T15-59-38@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38424) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGZ0v-0007N3-TW for emacs-orgmode@gnu.org; Mon, 12 Dec 2016 17:24:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cGZ0q-0004E0-U0 for emacs-orgmode@gnu.org; Mon, 12 Dec 2016 17:24:05 -0500 Received: from smtp3.tech.numericable.fr ([82.216.111.39]:49362) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cGZ0q-0004DE-NC for emacs-orgmode@gnu.org; Mon, 12 Dec 2016 17:24:00 -0500 In-reply-to: <2016-12-12T15-59-38@devnull.Karl-Voit.at> 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: Karl Voit Cc: emacs-orgmode@gnu.org Hi all, Karl Voit writes: > Oh my goodness - free wishes for org-depend? Christmas is rather > early this year! ;-) Indeed, that's wonderful ^^ > OK, let's do some brain storming ... As a summary from my sight point, I am totally inline with Karl for the feature set: - Personnally, I am ready to care about state consistency myself, so letting the user responsible for it - Same wish about scheduling arbitrary actions by making use of IDs: either absolute or relative - I would also have use of different state transitions: DONE => TODO ; CANCELLED => CANCELLED Besides that, I wonder if/how we could automate the following course of actions: - let have point on an entry - create a new "TODO-like" entry as a link to that entry - assign an ID to both entries: lets say "ID-original" and "ID-duplicate" - in the new entry: define a BLOCKER property set on "ID-original" - in the original entry: define a TRIGGER property set as ID-duplicate(DONE) At first sight: - the new entry could be created besides the original or in a file where it is ready to refile - the TODO state in the new entry could be set with a default, I think it is so easy to switch afterwards with Org keystrokes - the triggered state might better be a parameter (possibly a customized default as "TODO"): otherwise, it would be necessary to go inside the drawer to change it Currently, I am doing all this manually, quite often. I am not sure if a capture template can offer that. It's on my plan to look after it for some time, but I didn't do it yet. The tricky part is the cross-link creation and storage. So, as we are discussion on the topic, I just share what is on my mind about it :) I wish it can bring something useful, Feedbacks are welcome, Christophe -- ---------------> mailto:R3vLibre@citadels.eu Once it's perfectly aimed, the flying arrow goes straight to its target. Thus, don't worry when things go right. There will be enough time to worry about if they go wrong. Then, it's time to fire a new arrow towards another direction. Don't sink. Adapt yourself ! The archer has to shoot accurately and quickly. [Words of Erenthar, the bowman ranger] <---------------<<<<