From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] Bugs for Emacs Lisp code blocks
Date: Sun, 07 Apr 2013 17:47:11 +0200 [thread overview]
Message-ID: <86d2u6z6kg.fsf@somewhere.org> (raw)
In-Reply-To: 871uamo4e9.fsf@gmail.com
Hi Eric,
Eric Schulte wrote:
> Emacs Lisp is an exception in terms of colname processing, it has
> default header arguments set to pass column names through to the code
> block, where the processing may be done trivially in Emacs Lisp.
OK, but I don't understand the precedence of header arguments. I thought that
a header argument given on the code block preempted all the other values
(system-wide default for all languages, language defaults, file-wide
arguments, and subtree arguments).
Why isn't this true here as well?
>> * Call at export time
>>
>> #+call: ELisp-echo-1(data=input)
>>
>> I get:
>>
>> | id | var1 |
>> | id | var1 |
>> | obs1 | foo |
>> | obs2 | bar |
>>
>> Not at all what I was expecting...
>
> Agreed, I've just pushed up a fix, so the following now works.
>
> #+name: input
> | id | var1 |
> |------+------|
> | obs1 | foo |
> | obs2 | bar |
>
> #+name: ELisp-echo-1
> #+begin_src emacs-lisp :var data=input :exports results
> data
> #+end_src
>
> #+call: ELisp-echo-1(data=input)
>
> #+RESULTS: ELisp-echo-1(data=input)
> | id | var1 |
> |------+------|
> | obs1 | foo |
> | obs2 | bar |
>
> Thanks for pointing this out.
Here, I understand that the #+call line uses the default header argument set
on the language. So, that seems right to me as well...
Thanks.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-04-07 15:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 15:44 [babel] Bugs for Emacs Lisp code blocks Sebastien Vauban
2013-04-07 13:29 ` Eric Schulte
2013-04-07 15:47 ` Sebastien Vauban [this message]
2013-04-07 19:42 ` Eric Schulte
2013-04-08 20:14 ` Sebastien Vauban
2013-04-08 21:07 ` Eric Schulte
2013-04-09 8:13 ` Sebastien Vauban
2013-04-12 22:03 ` Eric Schulte
2013-04-15 13:46 ` Sebastien Vauban
2013-04-09 19:46 ` Sebastien Vauban
2013-04-10 7:54 ` Sebastien Vauban
2013-04-12 22:10 ` Eric Schulte
2013-04-15 14:09 ` Sebastien Vauban
2013-04-15 15:26 ` Eric Schulte
2013-04-12 22:09 ` Eric Schulte
2013-04-15 14:04 ` Sebastien Vauban
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=86d2u6z6kg.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).