[slime-devel] Recursive edit?
Recently SLIME has started asking me a lot if I want to enter a recursive edit whenever it enters the debugger. If I say n it freezes until I C-g out. If I say y it seems okay. What's that all about? -Peter -- Peter Seibel peter@javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp
Peter Seibel <peter@javamonkey.com> writes:
Recently SLIME has started asking me a lot if I want to enter a recursive edit whenever it enters the debugger. If I say n it freezes until I C-g out. If I say y it seems okay. What's that all about?
When I had this problem it turned out to be a stale .elc file. Zapping slime.elc did the trick to fix it. HTH, YMMV, etc, Zach
Zach Beane <xach@xach.com> writes:
Peter Seibel <peter@javamonkey.com> writes:
Recently SLIME has started asking me a lot if I want to enter a recursive edit whenever it enters the debugger. If I say n it freezes until I C-g out. If I say y it seems okay. What's that all about?
When I had this problem it turned out to be a stale .elc file. Zapping slime.elc did the trick to fix it.
I just don't byte-compile SLIME at all (or, for that matter, any third-party Emacs software, unless it refuses to work without undergoing a "make install" that byte-compiles it in the process). never had any perceivable performance problems because of this. interpreted elisp is just Fast Enough. just a useless thought, --m -- Every program is a part of some other program and rarely fits. -- Alan Perlis
Michael Livshin <usenet@cmm.kakpryg.net> writes:
never had any perceivable performance problems because of this. interpreted elisp is just Fast Enough.
It is usually just Fast Enough, until you write loops with macros like loop or SLIME's destructure-case macro. SLIME already byte-compiles the most performance critical functions at load-time, so byte-compiling the entire file doesn't by very much. Helmut.
Peter Seibel <peter@javamonkey.com> writes:
Recently SLIME has started asking me a lot if I want to enter a recursive edit whenever it enters the debugger. If I say n it freezes until I C-g out. If I say y it seems okay. What's that all about?
SLIME enters a recursive edit when a synchronous RPC needs to be debugged. This is usually only needed to debug SLIME code with SLIME itself. Most RPCs -- in particular RPCs to evaluate arbitrary user code -- are asynchronous. So a recursive edit is usually a sign for a bug in a SWANK function. Helmut.
Helmut Eller <e9626484@stud3.tuwien.ac.at> writes:
Peter Seibel <peter@javamonkey.com> writes:
Recently SLIME has started asking me a lot if I want to enter a recursive edit whenever it enters the debugger. If I say n it freezes until I C-g out. If I say y it seems okay. What's that all about?
SLIME enters a recursive edit when a synchronous RPC needs to be debugged. This is usually only needed to debug SLIME code with SLIME itself. Most RPCs -- in particular RPCs to evaluate arbitrary user code -- are asynchronous. So a recursive edit is usually a sign for a bug in a SWANK function.
I belive that theory fits my observations--I *have* been mucking around with Swank code. So is the best thing to do to say 'y' and proceed on my way. -Peter -- Peter Seibel peter@javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp
participants (4)
-
Helmut Eller -
Michael Livshin -
Peter Seibel -
Zach Beane