From: Martin Halder <martin.halder@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: [Babel] size limit of #+call
Date: Sat, 24 Mar 2012 21:46:44 +0100 [thread overview]
Message-ID: <E2499970-8494-43F7-844F-6B3CFD71A543@gmail.com> (raw)
In-Reply-To: <32138.1332615602@alphaville>
Am 24.03.2012 um 20:00 schrieb Nick Dokos:
> Martin Halder <martin.halder@gmail.com> wrote:
>
>> Hi all,
>>
>> trying to use a function to output a latex file using python with =
>> #+call.
>>
>> The example below does work but when pycalltest gets too big it just =
>> output "nil".
>> When I call pycalltest directly with C-c C-c it works even with a big =
>> function.
>>
>> Is there a size limit when I use #+call ?
>>
>> Thanks for help,
>> Martin
>>
>> #+name: =
>> pycalltest(trans=3Dtranslation,items=3Ditems,cust=3Dcustomer,deta=3Ddetail=
>> s,lang=3D"german",cur=3D"chf")
>> #+begin_src python :results output
>> execfile('latex.py')
>> print lx_config
>> #+end_src
>> #+call: pycalltest(translation,items,customer,details,"german","chf") =
>> :file "test.tex"
>
> Can you please provide all the pieces needed to run this? I presume at least
> latex.py is needed - anything else?
could reduce the problem to a small example, seems the table is handled differently when using #+call.
direct evaluation:
[['country', 'Schweiz', 'Switzerland']]
using call:
[['field', 'german', 'english'], None, ['country', 'Schweiz', 'Switzerland']]
#+tblname: transl
| field | german | english |
|---------+---------+-------------|
| country | Schweiz | Switzerland |
#+name: pycalltest(trans=transl)
#+begin_src python :results output
print trans
#+end_src
#+call: pycalltest(transl) :file "test.tex"
next prev parent reply other threads:[~2012-03-24 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 18:39 [Babel] size limit of #+call Martin Halder
2012-03-24 19:00 ` Nick Dokos
2012-03-24 20:46 ` Martin Halder [this message]
2012-03-24 21:00 ` Martin Halder
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=E2499970-8494-43F7-844F-6B3CFD71A543@gmail.com \
--to=martin.halder@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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 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).