Greetings,
C-c C-c ie slime-compile-defun on a function with ccl will always define or redefine the function in the package CL-USER regardless of which package the repl is currently in, while with sbcl slime-compile-defun will change the function in the package that the repl is currently in which is pretty much what I want.
let me put this another way, with ccl whenever I change the current package of the repl to my own package instead of CL-USER then evalute the value of *package* by hitting C-x C-e in a lisp buffer connected to ccl will always give me the value #<Package "COMMON-LISP-USER">
Could swank-ccl be configured or tuned to behave like what swank-sbcl does?
Thanks, Darren.
Sorry, it's all my fault, actually it works quite well
I found the culprit: this line in my config file:
;;(setq slime-find-buffer-package-function 'find-mit-scheme-package)
The buffer's current package is determined by the line (in-package ...) in the buffer, the above line of config causes it not to work. I wonder why I always had got ? in the mode line which should be the name of the buffer's current package.
Sorry for the noise. It is really perfect!
C-c C-c ie slime-compile-defun on a function with ccl will always define or redefine the function in the package CL-USER regardless of which package the repl is currently in, while with sbcl slime-compile-defun will change the function in the package that the repl is currently in which is pretty much what I want.
-
Darren Hoo