From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gergely Polonkai Subject: Re: RFC: Extensible Dependencies 'N' Actions Date: Sat, 22 Apr 2017 05:23:52 +0000 Message-ID: References: <87pog5rx5g.fsf@escafil> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11410ef4121c2c054dba95f5 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34327) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d1nWi-0008R5-Fh for emacs-orgmode@gnu.org; Sat, 22 Apr 2017 01:24:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d1nWh-0003Uk-9n for emacs-orgmode@gnu.org; Sat, 22 Apr 2017 01:24:08 -0400 Received: from mail-lf0-x235.google.com ([2a00:1450:4010:c07::235]:34133) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d1nWh-0003US-28 for emacs-orgmode@gnu.org; Sat, 22 Apr 2017 01:24:07 -0400 Received: by mail-lf0-x235.google.com with SMTP id t144so53307424lff.1 for ; Fri, 21 Apr 2017 22:24:05 -0700 (PDT) In-Reply-To: <87pog5rx5g.fsf@escafil> 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: Ian Dunn , emacs-orgmode@gnu.org --001a11410ef4121c2c054dba95f5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello Ian, I just read the docs and I like it so far. There are three things I=E2=80= =99d mention: =E2=80=A2 Some finders have missing documentation (although their names are= pretty straightforward) =E2=80=A2 Why the =E2=80=9Cnew language=E2=80=9D, why can=E2=80=99t it be l= isp, or at least more lispish? =E2=80=A2 You gave us a possibility to create naming clashes between target= s, finders, etc. For example, I might want to file a note when a file of a project changes, so I use your file target, and create the file action. How will Edna know when to use which? Hope I helped. I=E2=80=99ll give Edna a shot on Monday and probably get bac= k with some results. Best, Gergely On Sat, Apr 22, 2017, 04:33 Ian Dunn wrote: > > I've been working on something akin to org-depend.el called org-edna. > Basically, Edna provides an extensible means of specifying blocking > conditions and trigger actions. > > For example, Edna allows you to specify that a task should be blocked > until all TODOs have been addressed in source code: > > > Or schedule the following task for an hour after the current task is > completed: > > > The (semi-complete) documentation is here: > http://www.nongnu.org/org-edna-el/ > > I'd appreciate some feedback on it, whether the code or the > documentation. > > -- > Ian Dunn > --001a11410ef4121c2c054dba95f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hello Ian,

I just read the docs and I like it so far. There are three t= hings I=E2=80=99d mention:

=E2=80=A2 Some finders have missing documentation (although = their names are pretty straightforward)
=E2=80=A2 Why the =E2=80=9Cnew language=E2=80=9D, why can=E2=80=99t it be l= isp, or at least more lispish?
=E2=80=A2 You gave us a possibility to create naming clashes between target= s, finders, etc. For example, I might want to file a note when a file of a = project changes, so I use your file target, and create the file action. How= will Edna know when to use which?

Hope I helped. I=E2=80=99ll give Edna a shot on Monday and p= robably get back with some results.

Best,
Gergely


On Sat, Apr 22, 2017, 04:33= Ian Dunn <dunni@gnu.org> wrote:=

I've been working on something akin to org-depend.el called org-edna. Basically, Edna provides an extensible means of specifying blocking
conditions and trigger actions.

For example, Edna allows you to specify that a task should be blocked
until all TODOs have been addressed in source code:


Or schedule the following task for an hour after the current task is
completed:


The (semi-complete) documentation is here:
http://www.nongnu.org/org-edna-el/

I'd appreciate some feedback on it, whether the code or the
documentation.

--
Ian Dunn
--001a11410ef4121c2c054dba95f5--