[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [BUG] Noweb reference eval syntax does not work

From: Charles C. Berry
Subject: Re: [O] [BUG] Noweb reference eval syntax does not work
Date: Thu, 4 Aug 2016 19:25:14 -0700
User-agent: Alpine 2.20 (OSX 67 2015-01-07)

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:


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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]