Open mashomee opened 3 years ago
Same problem here, my solution is to select RETURN-FROM-CALLBACK
from the restarts list in the debugger buffer instead of aborting thread by pressing 'q', 'a' or picking any other restart option.
Put (ql:quickload 'swank :silent t)
at the top of the main file and (swank:create-server :port 5555 :dont-close t)
somewhere near the end (after you have already called gtk:within-main-loop
), then start up the script with sbcl --load file.lisp
and connect to it with slime-connect
instead. This has worked well for me so far.
Currently once an error happened in the gtk main thread, I have to restart the inferior lisp or the following gtk windows will not show whether it's coded correctly or not .
Is there a way not need to restart slime-inferior lisp in case of gtk main thread error in emacs?