On 2013-07-03 13:23, Eric Schulte wrote:
Currently colnames are not used for emacs-lisp code blocks (for
historical reasons). Unfortunately, call lines are executed by
expanding first to a trivial emacs-lisp code block, which is then run
to
collect and possibly re-package the results of the ca
Currently colnames are not used for emacs-lisp code blocks (for
historical reasons). Unfortunately, call lines are executed by
expanding first to a trivial emacs-lisp code block, which is then run to
collect and possibly re-package the results of the called function.
Thus colnames do not work well
On 2013-06-30 19:21, Eric Schulte wrote:
Rick Frankel writes:
it seems that the :colnames header is not being respected on parsing
the
input
to a `#+call:' line containing arguments, but is being applied to the
output!
For example:
#+BEGIN_SRC org
* Identity
#+name: table
| a | b | c |
|---
Rick Frankel writes:
> it seems that the :colnames header is not being respected on parsing the
> input
> to a `#+call:' line containing arguments, but is being applied to the
> output!
>
> For example:
>
> #+BEGIN_SRC org
> * Identity
> #+name: table
> | a | b | c |
> |---+---+---|
> | 1 | 2 |
it seems that the :colnames header is not being respected on parsing the
input
to a `#+call:' line containing arguments, but is being applied to the
output!
For example:
#+BEGIN_SRC org
* Identity
#+name: table
| a | b | c |
|---+---+---|
| 1 | 2 | 3 |
#+name: identity
#+BEGIN_SRC emacs-lisp
