From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: [babel] is there a chance to split arguments in src block calls
 or noweb syntax
Date: Sun, 31 Jan 2016 11:34:26 -0800
Message-ID: <alpine.OSX.2.20.1601311116450.1553@charles-berrys-macbook.local>
References: <CAAjq1mfpesmRmfVnGmMhErZDH4Y+6h9xupgdxMtocF-ENkFtgg@mail.gmail.com>
	<56ADC60F.5080404@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55597)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ccberry@ucsd.edu>) id 1aPxla-0001SH-S7
	for emacs-orgmode@gnu.org; Sun, 31 Jan 2016 14:34:35 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ccberry@ucsd.edu>) id 1aPxlW-0000OL-RJ
	for emacs-orgmode@gnu.org; Sun, 31 Jan 2016 14:34:34 -0500
Received: from iport-acv5-out.ucsd.edu ([132.239.0.10]:22801)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ccberry@ucsd.edu>) id 1aPxlW-0000Np-Ie
	for emacs-orgmode@gnu.org; Sun, 31 Jan 2016 14:34:30 -0500
In-Reply-To: <56ADC60F.5080404@gmx.net>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: "O.Hamann" <O.Hamann@gmx.net>
Cc: emacs-orgmode@gnu.org

On Sun, 31 Jan 2016, O.Hamann wrote:

> Hi all,
>
> Splitting header arguments for source blocks into different lines works very 
> fine,
> (and leads one to put more and more args in the header... )
>
> Is there a chance or trick to do similarly when calling such src blocks?
> Somehow like in shell scripts a backslash at the end of a line will signal 
> continuation?
> (example see below)
>
> Any suggestions or workarounds or best-practices to make the call lines 
> better readable and editable are welcome!
>
> Kind regards,
>
> Olaf
>

Try using a custom babel language. Then using variable assignment from 
babel block.

Here I define `fundamental' as a language, which means I can edit src 
blocks like `lorem' in a src edit buffer in fundamental mode without 
needing to do more than execute the `define-fundamental-as-babel' block or 
put that defun in my .emacs. And when I execute the lorem block - as when 
it is used in `:var txt=lorem()' - it returns the body as a string.


#+NAME: define-fundamental-as-babel
#+BEGIN_SRC emacs-lisp
   (defun org-babel-execute:fundamental (body params)
     (format "%s" body))
#+END_SRC

#+NAME: lorem
#+BEGIN_SRC fundamental
   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
#+END_SRC

#+NAME: abc
#+BEGIN_SRC emacs-lisp :results value :var txt="A B C"
(concat "txt-->" txt "<--txt")
#+END_SRC

#+CALL: abc( lorem() ) :results raw :wrap EXAMPLE

#+RESULTS:
#+BEGIN_EXAMPLE
txt-->Lorem ipsum dolor sit amet, consectetuer adipiscing elit.<--txt
#+END_EXAMPLE


BTW, there is already `org-babel-execute:latex', which is very handy for 
editing LaTeX and then handing it to a src block for further processing.

HTH,

Chuck