wxMaxima version: 26.01.0_MSW
Using wxWidgets version: wxWidgets 3.2.9
Maxima version: 5.49.0
Maxima build date: 2026-01-02 21:27:51
Host type: x86_64-w64-mingw32
System type: Win32 10.0.19041 X86-64
Lisp implementation type: SBCL
Lisp implementation version: 2.6.0
This is just a short example of the infinity of code,programs in which the only way out is end the
program or ctrl-alt delete. cannot restart maxima nor interrupt
for i thru i+1 do disp(i)
It is especially frustrating when have such as this in a long program where one loses all which
has happened several times in the past mostly on prior versions but this shows same bug or
fault in the latest version of maxima.
Could be fault of Microsoft as you are probably restricted to ring 4 of the microprocessor for
otherwise if you were in ring one could do assembly language routine to get a hold of the
interrupts that happen many times per second. Maybe one could also in ring 4 not sure which
is why all should be written in assembly language if getting a hold of interrupt not available
otherwise. In any event if possible in Microsoft windows should do that before losing all work and
program progression etc. in a long involved program.
I think I already told you that this is not a bug in Maxima, but in the front-end wxMaxima, and it should be reported there: https://github.com/wxMaxima-developers/wxmaxima/issues
Using Microsoft Windows, a workaround is to use the Windows Task manager. Once you start the Task manger, search for "SBCL." Then select it and then select "end the task" After that, you can likely restart Maxima and your wxMaxima will be preserved.
actually you told me the cannot signal interrupt was a wxmaxima issue. was not sure if this
issue was or was not.
Try running Maxima in a terminal window. You will discover that cntrl-c works correctly.
Thus, this is a problem with wxMaxima, not Maxima. The wxMaxima developers are active and good about fixing bugs, so please report it to them.
not sure exactly what a terminal window means For some other cases I can do ctrl I and it works
but i think that was with prior version of maxima. I think you were mistaken when you wrote ctrl c and meant ctrl i ? By the way this was not a duplicate of the last report. That one was a longer command and one could restart maxima from within the session. This is different as just an example of one cannot even restart maxima within the maxima interface as like keyboard is locked and does nothing . The last one reported one could use keyboard within the maxima session. But for this one is completely locked out cannot even do alt M and choose restart maxima while for that last one you could. Anyway i reported it to the wxmaxima over 5 days ago and they have yet to respond.
I have no windows box to test that on. Isn't interrupt Ctrl+G?
Kind regards,
Gunter.