On Wednesday 13 October 2004 22:22, James Amundson wrote:
> You are working much, much too hard. You appear to think that Maxima's
> interface is stuck in the stone age. With the release of Maxima 5.9.1,
> however, we are now firmly in the bronze age. (You did read the release
> notes for 5.9.1, didn't you?) There is some very terse documentation
> available in doc/implementation/external-interface.txt. As an example,
> put the following in a file called interface-example.lisp:
>
Abdulhaq: Puts down piece of flint and picks up chisel...
>
> You might also find using the socket interface via
> maxima --server=4008 --preload-lisp=interface-example.lisp
> to be superior to messing around with pyexpect. Maybe you won't, I don't
> know. The socket interface is, unfortunately, undocumented. The one
> trick to know is that the maxima "server" is really a socket client. The
> gui has to be the socket server.
>
> OK, I see that you haven't read the release notes for 5.9.1. Please read
> the file NEWS in the 5.9.1 tarball.
>
That's very helpful, thanks. Before switching to the socket version, can you
tell me if it improves this problem:
On entering:
(%i1) integrate(,x);
Maxima sends out three input prompts with various error messages. The problem
is, how does the GUI client know that Maxima has finished sending data? At
the moment I keep waiting for Maxima after a syntax error and if I get no
reply after one second then I assume Maxima has finished. What I would like
is some sort of terminator from Maxima to say 'Done, awaiting input'
Thanks again for your help
Abdulhaq