Hi again,
as a follow up: I can't believe how far behind my org version was (I
suppose I was running the built-in version).
Now that I have upgraded to 9.0.3, your code works like a charm.
Thanks again,
Sébastien
2017-01-21 6:30 GMT+01:00 Sébastien Brisard :
> Hi Chuck,
Hi Chuck,
thank you *very much* for this answer!
I was indeed wondering what was the entry point into the org source
for this. `org-babel-ref-resolve' is where I should start. I'm still
relatively new to emacs-lisp and do not know how to instrument the
code in order to trace all calls (which would
On Thu, 19 Jan 2017, Sébastien Brisard wrote:
Thanks Charles for this answer. Let me state the problem more clearly.
Number-like cells *are* converted to numbers (as best illustrated by
the example below (see the use of numberp), which might incur accuracy
loss (see below, the first row has a
Thanks Charles for this answer. Let me state the problem more clearly.
Number-like cells *are* converted to numbers (as best illustrated by
the example below (see the use of numberp), which might incur accuracy
loss (see below, the first row has a lot of significant digits).
I am not interested in
On Thu, 19 Jan 2017, Sébastien Brisard wrote:
Hello all,
here is a MWE
=BEGIN MWE=
#+NAME: table20170119
| col1 | col2 |
|--+|
| row1 | 1234567890 |
| row2 | a |
| row3 | b |
| row4 | c |
#+BEGIN_SRC emacs-lisp :var table=table20170119
Hello all,
here is a MWE
=BEGIN MWE=
#+NAME: table20170119
| col1 | col2 |
|--+|
| row1 | 1234567890 |
| row2 | a |
| row3 | b |
| row4 | c |
#+BEGIN_SRC emacs-lisp :var table=table20170119 :colnames yes :results output
(print (map