--- Jay Belanger <belanger@truman.edu> wrote:
>
> C Y <smustudent1@yahoo.com> writes:
> The problem was that multicol uses \output, so when EMaxima redefined
> \output, it caused errors when multicol was used.
> So I changed EMaxima so it doesn't use \output anymore.
> I changed all variables to make sure they contain some form of
> "maxima", so there shouldn't be any more conflicts.
Great! Works like a charm.
> > Also, would there be any way to add into emaxima mode the ability
> to
> > generate sessions of the kind that batlatex does, so we can have
> all
> > the abilities in one package?
>
> emaxima-mode now has session cells, which begin and end with
> \beginmaximasession
> and
> \endmaximasession
> and will result in the input and output being together with the
> Maxima prompts. (It doesn't yet do the nice colors and TeX output
> that batlatex does, though.)
I've been trying that out, and so far it looks excellent. Do you think
there is any way to add the TeX stuff at some point in the future? If
so, I can shift entirely to emaxima for doing manual stuff. No big
deal in any case - this is really excellent work.
So far, in trying the session environment out, I've stumbled onto one
thing that should probably be fixed - if a quit(); command is included
in a session it hangs emacs. Granted that probably won't be a command
included real often, but still it should probably fail cleanly.
We all owe you a vote of thanks for the magnificent work you've been
doing here, Jay. I've little doubt this will become the standard
maxima interface for the forseeable future.
__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1