Re: [Maxima-commits] CVS: maxima/lisp-utils maxima-run-lisp,1.2,1.3



>>>>> "James" == James Amundson <amundson@users.sourceforge.net> writes:

    James> Update of /cvsroot/maxima/maxima/lisp-utils
    James> In directory usw-pr-cvs1:/tmp/cvs-serv8792/lisp-utils

    James> Modified Files:
    James> 	maxima-run-lisp 
    James> Log Message:
    James> Hardcode "(user:run)" for running with cmucl, instead of saving it as
    James> the init function. This is really a big hack. It should be addressed
    James> in a more general manner.

Hmm, I think this change changes how cmucl behaves.

Before, when I run maxima with cmucl and press control-c, I'd get
something like:

        Interrupted at #xFF217D00.

        Restarts:
          0: [CONTINUE    ] Return from BREAK.
          1: [MACSYMA-QUIT] Macsyma top-level

And pressing 0 or 1 would do what I wanted.  

Now it says:

        Interrupted at #xFF217D00.

        Restarts:
          0: [CONTINUE    ] Return from BREAK.
          1: [MACSYMA-QUIT] Macsyma top-level
          2: [ABORT       ] Skip remaining initializations.


I don't think option 2 should be allowed.  It brings us back to the
top-level cmucl that thinks it's still running the initialization
code.  

I don't know how to fix this, if, indeed, it is a bug.

Ray