emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: dieter@duenenhof-wilhelm.de
Cc: "Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: #+header keywords for #+call keyword?
Date: Wed, 24 Jul 2013 16:35:31 -0600	[thread overview]
Message-ID: <87mwpboaa0.fsf@gmail.com> (raw)
In-Reply-To: CAPM452p8JWsZUnmXj45jHk=NWM-n=3yb5kPMYyuR0iWAAWodmg@mail.gmail.com

"Dieter Wilhelm, H." <dieter@duenenhof-wilhelm.de> writes:

> Dear (),
>
> I've got a rather long argument list and it doesn't look good to
> supply all the arguments in one line, could somebody please implement
> #+header arguments for #+call like in the following example?
>
> #+header: :var NO=(org-entry-get nil "Report_Dir")
> #+header: :var DIR=(org-attach-dir)
> #+call: ProvideReport()[:results silent]
>
> By the way, is it still true that the number of #+header keywords for
> code blocks is restricted to 5 #+header lines?  I think this is also
> an unnecessary restriction.
>
> Thank you very much
>

The #+call: line syntax is a shortened syntax for code blocks.  They
recently got #+names, hopefully soon they will get #+header arguments as
well.  In the interum, you can always use a code block

    #+header: :var NO=(org-entry-get nil "Report_Dir")
    #+header: :var DIR=(org-attach-dir)
    #+call: ProvideReport()[:results silent]

can be replaced by

    #+header: :var NO=(org-entry-get nil "Report_Dir")
    #+header: :var DIR=(org-attach-dir)
    #+begin_src emacs-lisp :var result=ProvideReport() :results silent
      result
    #+end_src

Best,


>
>   Dieter
> --
> Best wishes
>
>     H. Dieter Wilhelm
>
> Darmstadt
> Germany
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

  parent reply	other threads:[~2013-07-24 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 12:11 #+header keywords for #+call keyword? Dieter Wilhelm, H.
2013-07-24 20:27 ` Torsten Wagner
2013-07-24 22:35 ` Eric Schulte [this message]
2013-07-25  6:31   ` Dieter Wilhelm
2013-07-25 13:37     ` Eric Schulte

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=87mwpboaa0.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=dieter@duenenhof-wilhelm.de \
    --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).