OK, it turns out I did not correct install Cantor after compiling it
(incorrect installation prefix). However, I've now fixed that
problem, and the result is that Cantor loads the Maxima init file
successfully and Maxima does honor the prompt prefix and suffix
variables, as verified by strace.
tags 737198 unreproducible
thanks
Greetings, and thanks so much for looking into this. To the OP, please
let me know if anything has been overlooked. If not, I plan on closing
this in a week's time.
Take care,
Robert Dodier robert.dod...@gmail.com writes:
OK, it turns out I did not correct
I've managed to build and install the current version of Cantor from Git.
Cantor reports its version as 0.5.
KDE version is 4.8.5.
Maxima version is branch_5_33_base_153_ge30d638 (post-5.33 from Git).
When I launch Cantor, :lisp *alt-display2d* is nil, which indicates
that cantor-initmaxima.lisp
I installed (via apt-get) cantor and cantor-backend-maxima on my
Ubuntu 12.04 system.
$ cantor --version
Qt: 4.8.1
KDE Development Platform: 4.8.5 (4.8.5)
Cantor: 0.3
When I launch cantor --backend maxima, it seems to work as expected.
However, I find that the variables and functions defined in
forwarded 737198 maxima-disc...@lists.sourceforge.net
thanks
Package: maxima
Version: 5.32.1-1
Severity: normal
Tags: upstream
Hi,
Running the unittests in cantor I found that maxima is not honouring the
*prompt-prefix* and *prompt-suffix* as are set by cantor (and documented in
maxima's
Package: maxima
Version: 5.32.1-1
Severity: normal
Tags: upstream
Hi,
Running the unittests in cantor I found that maxima is not honouring the
*prompt-prefix* and *prompt-suffix* as are set by cantor (and documented in
maxima's doc/implementation/external-interface.txt).
cantor uses
6 matches
Mail list logo
