Dan Davison stats.ox.ac.uk> writes:
>
> Hi Juan and d.tchin,
>
> One thing I'd like to ask for advice about is the behaviour of tabular
> data structures containing strings. For example
>
> #+begin_src octave
> ans = [['a','b'];['c','d']]
> #+end_src
>
> #+results:
> : acbd
>
> I don't know
Hi Juan and d.tchin,
One thing I'd like to ask for advice about is the behaviour of tabular
data structures containing strings. For example
#+begin_src octave
ans = [['a','b'];['c','d']]
#+end_src
#+results:
: acbd
I don't know if my syntax above is correct, but it seems to me that this
is a 2x
Juan writes:
> Hi,
>
> I'm starting to work with ob-octave and found several problems:
Hi Juan,
Thanks very much. I've applied your patch with one minor change:
(format "%s" (or var "nil"))
However, is there a better way to receive an elisp nil value in octave?
> I'm not working with session
Hi,
Below is a single PATCH for the 3 issues:
- passing tables with EXP or complex notation to octave
- correct formatting of matrixes into octave
- interpretation of octave output as table
Regards,
.j.
8<
diff --git a/lisp/ob
Hi,
I'm starting to work with ob-octave and found several problems:
The first, for which I have a fix (see patch below) is that octave's
output was passed on as a string instead of being interpreted as a table:
8<
diff --git a/lisp/ob-o
