Menu
▾
▴
#3100 How to make Maxima hang in no time, with two simple moves
The recipe:
1) Hit the ESC key, and then ENTER (or SHIFT+ENTER, depending on your setup).
2) If the Maxima doesn't hang, then do it again. This time it will for sure.
build_info(version="5.37.3",timestamp="2016-01-11 20:53:44",host="i686-pc-mingw32",lisp_name="GNU Common Lisp (GCL)",lisp_version="GCL 2.6.11")
More on this:
Hitting the ESC button created a special character "¦" which Maxima tries to parse, and hence hangs.
Furthermore, if the ESC key is hit anywhere during the job without hitting the ENTER, and the job is saved at some point, the special character "¦" gets saved too. So it is very likely that it will make the Maxima hang the next time the file is loaded and executed. It can be a pain to detect and debug, especially when the input cells are made of tens of lines, as mine usually are.
I think this should be fixed, but you folks decide.
Hi,
I cannot reproduce your bug either in Maxima or in Xmaxima. For one thing, my keyboard doesn't give a character "¦" when I hit ESC, but even if I paste that character and hit enter, Maxima doesn't get stuck. Are you by any chance using Wxmaxima?
Hi Jaime.
Ehm... Yes I do. So you say it could be a Wxmaxima problem? But the odd thing is that you cannot reproduce the problem even by copy-pasting the special character. So then Wxmaxima is passing to Maxima something different from the "¦" character, which is odd.
Do you think it would be a good thing to have at least one more confirmation that Wxmaxima is the culprit, before closing this report?
I don't know if it's a Maxima or a Wxmaxima problem, but I cannot find out because I don't use Wxmaxima. Therefore, I'm saying that this bug should be sent first to the Wxmaxima tracking system and only if they come to the conclusion that it's a Maxima bug it should then be submitted here.
I typically use rmaxima with vi key bindings where ESC is used to switch modes (so no problem there...). I also cannot reproduce the problem with Xmaxima.
I agree that this should be sent to Wxmaxima.
Ok, I've created a bug report to Wxmaxima discussion board: https://sourceforge.net/p/wxmaxima/discussion/435775/thread/ae8aa3ba/
Thank you.
I'm closing this as "won't fix" since it seems to be a bug in wxMaxima.
theres a million and one ways to make it crash very easily - and the only way out is ctrl-alt-delete and lose all your work has happenned all too often ! That ctrl I for interrupt is about the most useless command there ever was - never works when u need it if at all. And all too often one loses all control of the keyboard, mouse or anything . Trying alt-M and choosing restart maxima is impossible. They should really have done assembly language coding and not totally lose control of what is going on - watchdog interrupt every so often no matter what.
In the last version several 100 bugs in wxMaxima have been resolved => I beg you to update to the current version that should resolve the "Esc" bug, as well, as the "Ctrl+I" one. If there still is a problem it often is near-to-impossible to tell if maxima or wxMaxima has caused it. But if wxMaxima causes it and it is reported at https://github.com/wxMaxima-developers/wxmaxima/issues I'll try to do my best to fix the bug.
Have you considered working with maxima in emacs?
Btw, many of your bug reports are better handled on the maxima-discuss
email list.
try ctrl I on:
for i thru i do disp(i)