From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles C. Berry" Subject: Re: [BUG] Noweb reference eval syntax does not work Date: Thu, 4 Aug 2016 19:25:14 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42339) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVUp8-0003Qo-Vb for emacs-orgmode@gnu.org; Thu, 04 Aug 2016 22:25:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bVUp4-0005Ht-QD for emacs-orgmode@gnu.org; Thu, 04 Aug 2016 22:25:21 -0400 Received: from iport-acv4-out.ucsd.edu ([132.239.0.7]:19343) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVUp4-0005Hj-H5 for emacs-orgmode@gnu.org; Thu, 04 Aug 2016 22:25:18 -0400 In-Reply-To: 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: Karsten Schmidt Cc: emacs-orgmode@gnu.org On Thu, 4 Aug 2016, Karsten Schmidt wrote: > Hi all, > > sorry for coming in super late to this thread, but I'd like to make a > plea to *not* deprecate the :noweb-ref header arg. > > On 12 May 2016 at 19:35:15, Aaron Ecay wrote: > >> To put it another way: it seems to me that the functionality of >> :noweb-ref can be reimplemented in terms of other primitives. Maybe you should respond to Nicolas' last posting in this thread: https://lists.gnu.org/archive/html/emacs-orgmode/2016-05/msg00263.html However, it doesn't look like :noweb-ref functionality is going away, but it may be shifted to require a noweb reference *evaluation* of a src block or lob block or maybe an idiom that looks like such (with the reference name as an argument) to invoke it. When that change occurs, I expect that a replace-regexp would be enough to update a file that uses :noweb-ref. If you want to get ahead of that change, you can probably assume that :noweb-ref headers will continue to exist and roll your own src block to handle the invocation. `(org-babel-map-src-blocks nil BODY)' with a suitably tooled BODY seems like it would be enough. See the docstring. If you require chained *evaluation* (including the _results_ of chained src blocks rather than just the src block bodies), you might show an example. So far, there hasn't been much concern that chained *evaluation* is useful. But it can be supported via the lob/src block gambit and you might get some tips on how to implement that or maybe convince someone to create a lob block that handles your case. HTH, Chuck