"Steven E. Harris" seh@panix.com writes:
Moving the cursor down to, say, the "1:" line and pressing enter to expand the frame causes XEmacs to hang. The minibuffer reports:
; pipelined request... (swank:frame-locals-for-emacs 1)
Sick. Does this happen consistently? I don't this problem with CLISP 2.33.2 on Debian.
The backtrace makes it look like Emacs is waiting to be told what the local variables are, but the event trace shows that this has been given. The "pipelined request" message is what you get when you make a request to Lisp before the result of the previous one has arrived.
Possibly the Emacs side is failing to recognise the RPC result, but that would be pretty extreme.