From: Dieter Wilhelm <dieter@duenenhof-wilhelm.de>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: "Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: #+header keywords for #+call keyword?
Date: Thu, 25 Jul 2013 08:31:57 +0200 [thread overview]
Message-ID: <874nbjgnfm.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <87mwpboaa0.fsf@gmail.com> (Eric Schulte's message of "Wed, 24 Jul 2013 16:35:31 -0600")
Eric Schulte <schulte.eric@gmail.com> writes:
> "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
I see, thank you, your suggestion is a already a good workaround for my
needs. :-)
Could you please also tell me whether you know of any restrictions
concerning the number of #+header lines before a code block?
--
Best wishes
H. Dieter Wilhelm
Darmstadt
Germany
next prev parent reply other threads:[~2013-07-25 6:34 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
2013-07-25 6:31 ` Dieter Wilhelm [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874nbjgnfm.fsf@duenenhof-wilhelm.de \
--to=dieter@duenenhof-wilhelm.de \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.