31 Jan
2010
31 Jan
'10
4:18 a.m.
This commit was a bad idea and has unforseen, undesirable consequences:
* 2009-10-15 Helmut Eller heller@common-lisp.net | | * slime-repl.el (slime-repl-find-buffer-package): New function. | (slime-repl-init): Initialize slime-find-buffer-package-function.
To use slime-repl-find-buffer-package this way, either slime-find-buffer-package-function should be made buffer local for "live" repl buffers, or much code needs to be redesigned to avoid redisplay errors, (when editing IN-PACKAGE forms, say), in a lisp buffer when slime is not connected to a lisp.
The attached backtrace may help you understand what I'm talking about.
--
Madhu
backtrace()
(or (slime-auto-connect) (backtrace) (error "Not connected."))
(cond ((and ... slime-net-processes) (or ... ...)) ((not conn) (or ... ... ...)) ((not ...) (error "Connection closed.")) (t conn))
(let ((conn ...)) (cond (... ...) (... ...) (... ...) (t conn)))
slime-connection()
(or process (slime-connection) (error "No connection"))
(process-buffer (or process (slime-connection) (error "No connection")))
(set-buffer (process-buffer (or process ... ...)))
(save-current-buffer (set-buffer (process-buffer ...)) slime-lisp-package:connlocal)
(with-current-buffer (process-buffer (or process ... ...)) slime-lisp-package:connlocal)
(slime-with-connection-buffer (process) slime-lisp-package:connlocal)
slime-lisp-package()
(or (slime-search-buffer-package) (slime-lisp-package))
slime-repl-find-buffer-package()
funcall(slime-repl-find-buffer-package)
slime-find-buffer-package()
(save-restriction (widen) (slime-find-buffer-package))
(or slime-buffer-package (save-restriction (widen) (slime-find-buffer-package)))
slime-current-package()
(let* ((conn ...) (local ...) (pkg ...)) (cond (... ...) (...)))
slime-modeline-string()
eval((slime-modeline-string))