emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "O.Hamann" <O.Hamann@gmx.net>
To: emacs-orgmode@gnu.org
Subject: [babel] is there a chance to split arguments in src block calls or noweb syntax
Date: Sun, 31 Jan 2016 09:30:07 +0100	[thread overview]
Message-ID: <56ADC60F.5080404@gmx.net> (raw)
In-Reply-To: <CAAjq1mfpesmRmfVnGmMhErZDH4Y+6h9xupgdxMtocF-ENkFtgg@mail.gmail.com>

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




What I mean:

#+NAME: namedSrcBlock
#+HEADER: :var arg1="val for arg1"
#+HEADER: :var arg2="val for arg2"
...
#+HEADER: :var argN="val for argN"
#+BEGIN_SRC
...
#+END_SRC

results in long call lines for #CALL: or noweb syntax hard to edit

#+CALL: namedSrcBlock(arg1="long argument value",arg2="even longer 
argument value",...,argN="many args later ")
<<namedSrcBlock(arg1="....",....,argN="...")>>


How to split those long lines, so that each arg-value pair stands on its 
own line?


The 'orgish' way would be sth like this, I guess:

#+CALL namedSrcBlock
#+ARGS: :arg arg1="..:"
#+ARGS: :arg arg2="..."
#+CALL_END

in noweb ref might be
<<namedSrcBlock(arg1="long argument value",\\SPACE
                    arg2="even longer argument value",\\SPACE
                    ... \\SPACE
                    argN="many args later")>>

But I did not find such anywhere.

  reply	other threads:[~2016-01-31  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-12  1:41 Noweb: Same function, two string results differ one with double-quotes the other without Grant Rettke
2016-01-31  8:30 ` O.Hamann [this message]
2016-01-31 19:34   ` [babel] is there a chance to split arguments in src block calls or noweb syntax Charles C. Berry
2016-02-05  7:49     ` O.Hamann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56ADC60F.5080404@gmx.net \
    --to=o.hamann@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).