Renier Marchand writes:
> It is a cool idea yes, but I quickly learned that it also have its
> problems, i.e. you cant really create nice column formulas because the
> reference is not aware of "the current row" etc.
>
> The biggest problem as I see it is that emacs-lisp does not support
> the co
It is a cool idea yes, but I quickly learned that it also have its
problems, i.e. you cant really create nice column formulas because the
reference is not aware of "the current row" etc.
The biggest problem as I see it is that emacs-lisp does not support
the complex data type as lisp (natively) do
Renier Marchand writes:
> I have found the following way to reference my data correctly without
> having to quote it or have data rewritten.
>
> I do:
>
> #+tblname: my-data
> | hmin |
> |--|
> | |
> | 0.05 |
> | 0.2 |
> | 0.2 |
> #+TBLFM
I have found the following way to reference my data correctly without
having to quote it or have data rewritten.
I do:
#+tblname: my-data
| hmin |
|--|
| |
| 0.05 |
| 0.2 |
| 0.2 |
#+TBLFM: @5$1='(sbe "myfunc" (data "my-data[3:4,0]"))
Th
Hi Eric
Thank you, that clarifies it quite a bit. Forgot about the lispyness
of the numbers in brackets.
Renier
On Wed, Apr 13, 2011 at 5:52 AM, Eric Schulte wrote:
> Hi Renier,
>
> The Org-mode table machinery is interpreting the values of your table
> cells as emacs lisp (given that the table
Hi Renier,
The Org-mode table machinery is interpreting the values of your table
cells as emacs lisp (given that the table formula is an elisp, rather
than a calc formula). Due to the "," the result is a weird nested list
which confuses your python code block. Some options here include...
1. wr
Hi.
I have been playing around with complex data that has been returned
from Python. This is obviously not in calc.el format but if I change
them to the correct format I can manipulate them using calc.
but
When I want to pass the complex numbers (python format) to python I
get an error. If I pas
