On Sat, Sep 13, 2008 at 11:12:29AM -0600, Robert Dodier wrote:
> On 9/13/08, Oliver Kullmann <O.Kullmann at swansea.ac.uk> wrote:
>
> > (%i1) batch("Batch.mac");
> > batching /home/csoliver/SAT-Algorithmen/OKplatform/Batch.mac
> > (%i2) for x in [1,2,3] do print(x)
> > 1
> > 2
> > 3
> >
> > Evaluation took 0.0000 seconds (0.0005 elapsed) using 4.250 KB.
> > (%o2) done
> > 0
> > (%i3) 10!;
> > Incorrect syntax: 10 is not an infix operator
> > 0\n10!
>
> Well, you entered just 0 not an entire input 0; or 0$ so
> the parser thinks you mean 0 10! as an input, which is invalid.
>
I know --- the point is that weird behaviour after that.
> What happens if you enter 0; after running the batch file?
>
With that one gets back into defined behaviour.
So well, then this is just the strange (and rather uncomfortable)
way the Maxima console behaves: It would be good if whatever
happened with Ctrl-C one would just return to the original state.
Worst is when it enters into "debugging mode": If one is lucky one
can escape, but after a wrong key stroke I never find back and have
to kill the session (potentially loosing data).
So well :-(.
Thanks!
I'll try the patch!
Oliver