From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Tangling takes long - profiling and calling R Date: Wed, 01 Jul 2015 15:03:03 +0100 Message-ID: <87zj3gj7qg.fsf@gmail.com> References: <87ioaobvl1.fsf@selenimh.access.network> <87a8vzc1u8.fsf@selenimh.access.network> <07F390A6-B112-4E02-8417-E9280B24AC94@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49855) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAIbj-00024A-Lo for emacs-orgmode@gnu.org; Wed, 01 Jul 2015 10:03:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZAIbd-0006ZE-Od for emacs-orgmode@gnu.org; Wed, 01 Jul 2015 10:03:23 -0400 Received: from mail-wg0-x234.google.com ([2a00:1450:400c:c00::234]:36841) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAIbd-0006Yo-H7 for emacs-orgmode@gnu.org; Wed, 01 Jul 2015 10:03:17 -0400 Received: by wguu7 with SMTP id u7so37788016wgu.3 for ; Wed, 01 Jul 2015 07:03:16 -0700 (PDT) In-Reply-To: <07F390A6-B112-4E02-8417-E9280B24AC94@gmail.com> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rainer M Krug , Sebastien Vauban Cc: "emacs-orgmode@gnu.org" Hello all, 2015ko ekainak 16an, Rainer M Krug-ek idatzi zuen: > I don't think that it is that easy, as the new syntax is not equivalent > to the old syntax. One example; defining one tangle target for the mother > tree, and others for the child trees. This is by no means trivial (or > even possible) with the new syntax, while it would be possible with the > old syntax (if I remember correctly). The last thread we had about this , we discussed some of the differences. Achim believed that some of them were due to bugs in the property API, but these have not been fixed (AFAIK). There is also a semantic difference in the two approaches as to whether a remote invocation of a babel block (via e.g. #+call) uses the properties from the block=E2=80=99s document position, or from the call=E2= =80=99s. Before deprecating the feature, the bugs should be fixed (if they are really bugs), and the semantic differences explicated better. --=20 Aaron Ecay