Bernd Weiss <bernd.we...@uni-koeln.de> writes:
[...]
> #+results:
> : incorrect syntax: / is not a prefix operator
> : incorrect syntax: aLH is not an infix operator
> : incorrect syntax: hCp is not an infix operator
> : incorrect syntax: Premature termination of input at $.
> : Maxima encountered a Lisp error:
> : parser: end of file while scanning expression.
> : Automatically continuing.
> : To enable the Lisp debugger set *debugger-hook* to nil.
>
> This message is 'related' (see lines 3 "aLH is not an infix operator"
> and 4 "hCp is not an infix operator") to the following Maxima call
> ("aLH/maxima-17716hCp"):
>
> maxima --very-quiet -r
> 'batchload("c:/Users/weiss/AppData/Local/Temp/babel-17716aLH/maxima-17716hCp")$'
> nil
The error messages look like maxima is trying to evaluate the actual
string within double quotes!
> Unfortunately, my elisp knowledge is too low to understand what's going
> on in ob-maxima.el. Is it a MS-Windows-thing ('/' vs '\')?
Good question. Has anybody else used maxima with org babel on Windows?
I don't even have such a system to try...
My guess would be that the "shell" command required to invoke maxima on
Windows needs to be significantly different than what we are using here
(which works on Linux). Then again, I've never really used Windows
(beyond starting Word on somebody else's document on somebody else's
machine... ;-) so I don't have a clue what Windows expects...
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.458.g1642)
