> Actually we found a usable solution (at least for maxima on UNIX
systems).
save(<<file>>,all) -- after kill(dva) -- works fine on my Windows 2000
system. In fact, all it does is enter the command for you -- you can
even look at its C-line:
(D8) ....
<<use menu: File / Save expressions / choose file >>
(C9)
<<notice the blank C-line output by Maxima>>
(C10) c9;
(D10) SAVE(C:/temp/foo2, ALL)
> save(...,all); appends a lot of "stuff" to the session, that
> cannot be interpreted by maxima.
There is actually only one thing causing problems: the compiled Maxima
macro definition 'dva'. That is why kill(dva) or redefining dva as a
non-compiled macro solves the problem. All the rest is actually useful:
things like the values of any variables you set, any functions you
defined, any match rules you defined, the settings of various flags,
etc. True, Maxima should probably do a better job of keeping track of
things that are predefined and not saving them, but that doesn't
normally matter.
If all you want is the labelled C and D lines, you can use
save(...,labels). That also avoids the bug.
-s