August 2004 - slime-devel - mailman3.common-lisp.net

[slime-devel] Is there some way to disconnect from SWANK quit emacs, and then reconect back without restarting SWANK?
by Ignas Mikalajūnas 16 Aug '04

16 Aug '04

I have tried doing this in several implementations: sbcl 8.7 sbcl 8.11 cmucl 19a cmucl 18e and failed all the time. slime-disconnect or slime-quit both make me reastart the swank by hand from lisp repl directly. Ignas Mikalajunas

3 2

[slime-devel] Allegro Doc Lookup
by Thomas Schilling 16 Aug '04

16 Aug '04

This is a (dirty) little hack to open the allegro docs from within Slime: (defun allegro-doc-lookup (symbol) (interactive (list (slime-read-symbol-name "Allegro Doc for: "))) (slime-eval-async `(cg:eval-in-listener-thread '(cl:let ((wnd (cl:make-instance 'cg:text-edit-window :name :get-help :owner (cg:screen cg:*system*) :state :shrunk :border :frame))) (cl:format (cg:frame-child wnd) "~a" ',symbol) (devel::windows-help-command wnd) (cl:close wnd))))) I didn't know where to integrate this in Slime (if even) so I thought this would be the best place to post it to. -ts

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 15 Aug '04

15 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.503 slime/ChangeLog:1.504 --- slime/ChangeLog:1.503 Fri Aug 13 14:27:08 2004 +++ slime/ChangeLog Sat Aug 14 15:10:20 2004 @@ -1,3 +1,8 @@ +2004-08-14 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-find-buffer-package): Use "%s", not "%S", to + avoid ugly escape characters, if the package name contains dots. + 2004-08-13 Luke Gorrie <luke(a)bluetail.com> * slime.el (sldb-eval-in-frame): Print result to the REPL when a

1 0

[slime-devel] slime-eval-last-expression in REPL
by Michael Weber 14 Aug '04

14 Aug '04

Calling C-x C-e (M-x slime-eval-last-expression) at a bare REPL prompt causes this: The variable CL-USER> is unbound. [Condition of type UNBOUND-VARIABLE] Restarts: 0: [ABORT] Abort handling SLIME request. 1: [DESTROY-THREAD] Destroy this thread (12715) GNU Emacs 21.3.50.1 SLIME CVS 2004/08/13 Cheers, Michael

2 1

[slime-devel] SB-EXT:RUN-PROGRAM and *STANDARD-OUTPUT* interaction in REPL
by Michael Weber 14 Aug '04

14 Aug '04

[Apologies, if this hit the list twice.] There seems to be some SLIME interaction between SBCL's SB-EXT:RUN-PROGRAM and *STANDARD-OUTPUT*. Consider this: (defun test (stream) (let* ((p (sb-ext:run-program "tr" '("a-z" "n-za-m") :input :stream :output stream :search t :wait nil)) (in (sb-ext:process-input p))) (format in "test~%") (sb-ext:process-close p) (sb-ext:process-wait p))) Executing (TEST T) causes the output go to emacs' *inferior-lisp* buffer, with (TEST *STANDARD-OUTPUT*) it goes to SLIME's REPL buffer, although they should behave the same, AFAICT. GNU Emacs 21.3.50.1 SLIME CVS-2004/08/13 SBCL 0.8.13 (I understand that this could just as well be an SBCL issue.) Now, why this function hangs after executing is another thing which I haven't figured out yet, but this is likely due to wrong use... Cheers, Michael

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 14 Aug '04

14 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.500 slime/ChangeLog:1.503 --- slime/ChangeLog:1.500 Thu Aug 5 08:19:24 2004 +++ slime/ChangeLog Fri Aug 13 14:27:08 2004 @@ -1,3 +1,29 @@ +2004-08-13 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (sldb-eval-in-frame): Print result to the REPL when a + prefix argument is given. + Added pull-down menus for SLDB and the REPL. + + * swank-source-path-parser.lisp: Removed caching of readtables and + the source-map hashtable. Fresh creation is ultra-cheap (<1ms). + The caching didn't handle modifications to readtables and + generally made me feel uneasy while tracking down an obscure bug + in a reader macro. + The cached source-map hashtable also wasn't thread-safe (ho hum). + +2004-08-13 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-merge-notes, slime-tree-for-note): Use the short + note message for annotation in the source buffer and the long + message in the tree widget. Used to be the other way around. + (sldb-insert-frames): Set the `start-open' property for XEmacs. + Without `start-open', the `point-entered' property is inherited + when we insert something before the "--more--" marker. Reported + by Sundar Narasimhan. + + * swank.lisp (variable-desc-for-echo-area): Bind some printer + variables to limit the length of the output. + 2004-08-05 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-setup): Added typeout-frame keyword argument.

1 0

[slime-devel] RFC: SLIME homepage suggestion
by Thomas Schilling 12 Aug '04

12 Aug '04

is it better now? http://www.inf.tu-dresden.de/~s3815210/slime-hp-suggestion/ -- ,, \../ / <<< The LISP Effect |_\\ _==__ __ | |bb| | _________________________________________________

5 12

[slime-devel] Editing previous input
by Pascal J.Bourguignon 12 Aug '04

12 Aug '04

In M-x shell, when you go anywhere in the buffer to edit any string (input by the user, part of the prompt (current directory path, etc), or output by previous commands, as soon as you type return, the current line is copied after the current prompt and executed. Surprizingly, slime does not behave similarly... Instead, it answers an unuseful: ; No value I think it'd be nicer to have a behavior similar to that of shell-mode. -- __Pascal Bourguignon__ http://www.informatimago.com/ Our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our country and our people, and neither do we.

2 1

[slime-devel] What should `M-x slime' do?
by Luke Gorrie 10 Aug '04

10 Aug '04

Ahoyhoy, A few times I've sat down to "fix" the behaviour of `M-x slime' and `M-x slime-connect' as regards multiple connections but I always give up and can't decide what they should do. Here are some cases: M-x slime, no prefix argument, already connected: Close all connections, but don't kill any inferior-lisps. If *inferior-lisp* exists then connect to that Lisp, otherwise start a new one and connect. .. or with prefix arg: Ask if we should create an additional connection. If yes, create a new *inferior-lisp* and connect. If no, do as above. M-x slime-connect, no prefix argument, already connected: Close all existing connections and then make the new one. .. or with prefix arg: Ask if we should close existing connections first. If yes, do as above. If no, keep existing connections and create a new one. Now that the protocol is robust I don't think you'd want `M-x slime' to reconnect to the current *inferior-lisp*, so maybe it should create an additional connection? And what about slime-connect? There's also the question of how we should recycle REPL buffers. I don't know if anyone has strong opinions on that. -Luke

4 3

[slime-devel] Finding source of functions compiled with slime-compile-defun.
by Peter Seibel 09 Aug '04

09 Aug '04

Again, having not looked into it in any great detail, is there any way to communicate source location back to Lisp so it can find the source of functions compiled with C-c C-c? -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

3 4

[slime-devel] multiprocessing, dll loading, slime, allegro 6.2 and windows
by Ian Eslick 09 Aug '04

09 Aug '04

I'm not sure this is the ideal forum for this slime-related bug, but I've discovered an odd interaction between slime, allegro 6.2, multiprocessing and foreign dll loading. Namely, I can load some dll's using (load "foo.dll") from within emacs/slime but others, say (load "test.dll"), fail from within emacs/slime but work fine in the same image when run from the console instead. Once the console loads the dll's, I can use them fine from within the slime buffer (def-foreign or uffi, etc). This may be a pure allegro/multiprocessing problem; but I wanted to see if anyone here has encountered similar problems or has a suggestion for diagnosing. Ian

2 1

[slime-devel] Weird interaction between CMU, SLIME, floating-point-modes, possibly kernel/chipset?
by rif 06 Aug '04

06 Aug '04

Sorry for the length of this post, but I'm encountering a very odd problem. This problem involves different behavior on two different x86 machines, one of which is a Dell Xeon desktop machine running Fedora Core with a 2.4.22 kernel, the other an IBM T42 laptop running Debian Testing with a 2.6.3 kernel. (The laptop has a Pentium M chip --- I do not know if this can be causing the differences, I guess the kernel difference seems more likely.) On both machines, I am using SLIME from CVS downloaded on 06 August 2004, and I'm using the CMUCL 19A binary release downloaded on 05 August 2004. Before each run of SLIME, I remove all the .x86f files from the slime directory, as well the entire ~/.slime directory, which seems to be caching these (this is probably overkill, but I don't have a good feel for what's being cached when I change things, and I'm trying to isolate the problem). In all cases, we consider a .emacs file consisting (only) of the following lines: (add-to-list 'load-path "/home/rif/Software/slime") (require 'slime) (setq swank:*communication-style* :sigio) (setq inferior-lisp-program "/home/rif/Software/CMU19A/bin/lisp") The .cmucl-init file is either blank, or consists of the single line: (set-floating-point-modes :traps nil) If the .cmucl-init file is not blank (contains the above line), at the CL-USER> prompt, I type: (get-floating-point-modes) If the .cmucl-init file IS blank, then I type at the prompt: (set-floating-point-modes :traps nil) (get-floating-point-modes) We consider a "correct" result to be (:TRAPS NIL :ROUNDING-MODE :NEAREST :CURRENT-EXCEPTIONS (:INEXACT) :ACCRUED-EXCEPTIONS (:INEXACT) :FAST-MODE NIL :PRECISION-CONTROL :64-BIT) We consider (:TRAPS (:OVERFLOW :INVALID :DIVIDE-BY-ZERO) :ROUNDING-MODE :NEAREST :CURRENT-EXCEPTIONS (:INEXACT) :ACCRUED-EXCEPTIONS (:INEXACT) :FAST-MODE NIL :PRECISION-CONTROL :64-BIT) to be an "incorrect result". On each of the two machines, I tested the empty and single-line .cmucl-init files inside and outside SLIME (outside SLIME means starting CMUCL in a terminal). On the desktop, everything gave the correct result. On the laptop, everything gave the correct result EXCEPT the combination of the blank initialization file and SLIME, which gave the incorrect result. For this combination, I also tried changing :sigio in the .emacs to :fd-handler, based on some earlier discussions on this list; this did not seem to make any difference. Summary: On my Dell machine, all methods give the correct result. On my IBM laptop, I do not have any way to set CMUCL floating-point modes on an already running SLIME, although I can do it either in a terminal or at SLIME start-up time. Any help or suggestions are appreciated. Sincerely, rif

2 3

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 06 Aug '04

06 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.498 slime/ChangeLog:1.500 --- slime/ChangeLog:1.498 Wed Aug 4 10:18:06 2004 +++ slime/ChangeLog Thu Aug 5 08:19:24 2004 @@ -1,3 +1,8 @@ +2004-08-05 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-setup): Added typeout-frame keyword argument. + (slime-thread-attach): Fixed misnamed function call. + 2004-08-04 Luke Gorrie <luke(a)bluetail.com> * swank-allegro.lisp (find-fspec-location): Fixed to work for more

1 0

[slime-devel] Using Allegro 6.2 for Windows with Slime
by Matthew Danish 05 Aug '04

05 Aug '04

I've noticed a few ad-hoc snippets of code to connect Slime to Allegro on Windows, and I thought that I should contribute my own. The primary advantage of this code is that it does not use a fixed port, but rather makes use of the existing Slime infrastructure to communicate a port number through a temporary file. Also, as a result, Slime will automatically attempt to retry connecting when it fails, which is better than having to worry about race conditions and timing issues. file load-slime.el: ;; This code derived from the Lisp in a Box project, hence the variable ;; names. The license for the project is the GPL. (defvar lispbox-base-path "c:/lisp") ; or wherever (defvar path-to-slime (concat lispbox-base-path "/slime")) (add-to-list 'load-path path-to-slime) (require 'slime) (slime-setup) (defun lispbox-start-allegro-6.2 () (let ((runallegro-path (concat lispbox-base-path "/Allegro62/RunAllegro.bat"))) (delete-other-windows) (shell-command (format "\"%s\" %s &" runallegro-path (slime-swank-port-file))) (slime-read-port-and-connect-to-running-swank nil) (add-hook 'kill-emacs-hook (lambda () (slime-repl-sayoonara))))) file (concat lispbox-base-path "/Allegro62/RunAllegro.bat"): @ECHO OFF C: CD "\lisp" "C:\acl62\alisp.exe" +B +cm -L "C:/lisp/slime/swank-loader.lisp" -e '(swank:start-server "%1")' Paths may have to be fiddled with, as appropriate. -- ; Matthew Danish <mdanish(a)andrew.cmu.edu> ; OpenPGP public key: C24B6010 on keyring.debian.org

2 2

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 05 Aug '04

05 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.495 slime/ChangeLog:1.498 --- slime/ChangeLog:1.495 Tue Aug 3 23:23:30 2004 +++ slime/ChangeLog Wed Aug 4 10:18:06 2004 @@ -1,3 +1,16 @@ +2004-08-04 Luke Gorrie <luke(a)bluetail.com> + + * swank-allegro.lisp (find-fspec-location): Fixed to work for more + types of definition than just functions. So M-. now works for e.g. + classes in Allegro. From Matthew Danish. + (find-fspec-location): Include the type of the definition in the + designator sent to Emacs. From Matthew Danish. + +2004-08-04 Martin Simmons <martin(a)xanalys.com> + + * swank-lispworks.lisp (frame-actual-args): Correct syntax for + handler-case. + 2004-08-04 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el: (slime-mode-map, slime-repl-mode-map)

1 0

[slime-devel] C-g after C-c ==> debugger
by Chisheng Huang 04 Aug '04

04 Aug '04

Typing C-g after C-c in a buffer editing a Lisp file will get a *sldb* buffer to show up: Error in function NIL: Interrupt from Emacs [Condition of type SIMPLE-ERROR] Restarts: 0: [CONTINUE] Continue from interrupt. 1: [ABORT] Abort handling SLIME request. 2: [ABORT] Return to Top-Level. Backtrace: ... I find myself getting thrown into a debugger this way quite a few times everyday. Could someone make Slime handle C-g better after a C-c? Thanks a lot. Best, -cph

5 8

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 04 Aug '04

04 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.494 slime/ChangeLog:1.495 --- slime/ChangeLog:1.494 Sun Aug 1 22:27:07 2004 +++ slime/ChangeLog Tue Aug 3 23:23:30 2004 @@ -1,3 +1,11 @@ +2004-08-04 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el: (slime-mode-map, slime-repl-mode-map) + (slime-repl-read-mode-map): Remove the binding for C-c C-g. C-c + C-b is now the default interrupt key. + (slime-list-repl-short-cuts): Don't trash the shortcut-table: copy + it before sorting. (Thanks to Mark Simpson.) + 2004-08-02 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-connect): Shorten the welcome message by leaving

1 0

[slime-devel] Shortcuts disappearing?!
by Person or Persons Unknown 04 Aug '04

04 Aug '04

(I just tracked the reason for a problem i have been seeing... hopefully this is the right place to provide bug reports and patches.) I started using SLIME at the 1.0 alpha stage and just updated to 1.0 beta tonight and still have a problem with shortcuts disappearing. The session will start out with all the shortcut commands but after some actions i will only have a short list of shortcut commands. I can consistently cause the problem by starting up SLIME, bringing up the shortcut help (via ,help) and then trying to do it again (i actually lose the help short cut so it fails! ,? will show two or three shortcuts now). The problem seems to be coming from the use of SORT* in SLIME-LIST-REPL-SHORT-CUTS. SORT* is a destructive function so the SLIME-REPL-SHORTCUT-TABLE is being trashed. Changing the code to call COPY-SEQUENCE on SLIME-REPL-SHORTCUT-TABLE before calling SORT* seems to do the trick. Thanks for SLIME, it is really slick! -Mark Simpson

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 03 Aug '04

03 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.488 slime/ChangeLog:1.489 --- slime/ChangeLog:1.488 Mon Jul 26 04:50:19 2004 +++ slime/ChangeLog Wed Jul 28 14:15:30 2004 @@ -1,3 +1,18 @@ +2004-07-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-eval-feature-conditional): Treat uppercase + operators NOT, AND, OR correctly. + (sldb-find-buffer): Remove killed buffers. + (sldb-quit): Raise an error if the RPC returns. + (slime-expected-failures): Delete unused function. + (complete-symbol): Test completion of + swank::compile-file. LispWorks has extra completions for + cl::compile-file. + (arglist): Test arglist of method cl:class-name. Add enough + regexpery to pass the test in most implementations. + + * swank-sbcl.lisp (list-callers, list-callees): Implemented. + 2004-07-26 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-first-change-hook): Add `save-match-data' to

3 5

[slime-devel] swank/xref and slime-load-file
by Jonathan Meeks 02 Aug '04

02 Aug '04

I think there is a bug in slime-load-file. I have noticed that when a file has its *.lisp extension in the parameter to slime-load-file, swank/xref is not able to find its callees (with slime-list-callees). When called interactively, the extension is stripped and slime-list-callees works. So, shouldn't the extension be stripped by slime-load-file when called non-interactively, as well? --Jonathan Meeks

3 3

[slime-devel] Extra Swank threads after slime-disconnect
by Alan Caulkins 02 Aug '04

02 Aug '04

Hello list, To start, I'm new to the list, and I'd like to congratulate everyone on creating such a wonderful piece of software. I've been continually impressed by SLIME ever since I started keeping up with it a few months ago. However, I think I've found a bug in Swank's spawn connection-style. I've been connecting to an already-running sbcl (on Linux) as per the instructions found on on Bill Clemenson's weblog, linked from CLiki's SLIME-HOWTO page. fatman@hubris:~$ sbcl --load slime.lisp This is SBCL 0.8.13, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. . <snip> . ;; Swank started at port: 4005. * My slime.lisp is simple: (load "lib/emacs/slime/swank-loader.lisp") (swank::create-swank-server 4005 :spawn #'swank::simple-announce-function t) Before connecting to Swank for the first time, there are 2 sbcl threads running: fatman@hubris:~$ ps -e | grep sbcl 9831 pts/0 00:00:04 sbcl 9832 pts/0 00:00:00 sbcl After running (slime-connect "localhost" 4005), we also see the new reader, control, and repl threads: fatman@hubris:~$ ps -e | grep sbcl 9831 pts/0 00:00:04 sbcl 9832 pts/0 00:00:00 sbcl 9844 pts/0 00:00:00 sbcl 9845 pts/0 00:00:00 sbcl 9846 pts/0 00:00:00 sbcl CL-USER> (in-package swank) #<PACKAGE "SWANK"> SWANK> (mapcar (lambda (c) (list (connection.control-thread c) (connection.reader-thread c) (connection.repl-thread c))) *connections*) ((9844 9845 9846)) But, after running (slime-disconnect), only the reader thread has terminated: fatman@hubris:~$ ps -e | grep sbcl 9831 pts/0 00:00:04 sbcl 9832 pts/0 00:00:00 sbcl 9844 pts/0 00:00:00 sbcl 9846 pts/0 00:00:00 sbcl With each successive connection and disconnection, two more threads are added. I suspect that's not the intended behavior. :) First of all, does this happen to anyone else? I'm using the laterst release of SBCL and the 1.0 Alpha release of SLIME, but some of my system libraries are pathetically out of date. I wouldn't be surprised to learn that my own system is the problem. Secondly, assuming this is a bug, I have come up with a fix. I simply defined a function for the :cleanup slot in the connection struct. My fix is decidedly simple-minded - I just kill the other two threads. It seems to work, but I have no idea if those threads were left alive for some reason, or if there is a better way to get them to terminate. Also, I'm still very new to the Lisp game, and although I've tried to honor your indirection and abstractions, I have no idea if I succeeded. -Alan PS- I tried to make the following diff from the current CVS instead of 1.0alpha, but I got these kind of errors on the sbcl console when the connection was closed: debugger invoked on a UNDEFINED-FUNCTION in thread 10396: The function :DEBUG is undefined. Linux: The ultimate video game. fatman@hubris:~/lib/emacs$ diff slime.alan/swank.lisp slime-1.0alpha/swank.lisp 488,491d487 < (defun cleanup-connection-threads (connection) < (kill-thread (connection.control-thread connection)) < (kill-thread (connection.repl-thread connection))) < 599,600c595 < :serve-requests #'spawn-threads-for-connection < :cleanup #'cleanup-connection-threads)) --- > :serve-requests #'spawn-threads-for-connection))

2 2

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 02 Aug '04

02 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.493 slime/ChangeLog:1.494 --- slime/ChangeLog:1.493 Sat Jul 31 23:46:48 2004 +++ slime/ChangeLog Sun Aug 1 22:27:07 2004 @@ -1,3 +1,31 @@ +2004-08-02 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-connect): Shorten the welcome message by leaving + out the port number (which is displayed in the REPL anyway). This + avoids line-wrapping some messages of encouragement. + + * swank.lisp (with-buffer-syntax): Don't bind *readtable* to + *buffer-readtable* if they are already EQ. When we shadow this + binding the user can't assign *readtable* from the REPL so it's + best avoided when possible. + + * swank-allegro.lisp: Removed fwrapper-based code for inheriting + "swankiness" to newly spawned threads. This was fighting the + system and not the right thing. + + * slime.el (slime-choose-overlay-region): Tweaked the + multiline-annotation-avoidance code to work with forms not + starting with an open-paren, e.g. `(..) or #'(..). + (slime-update-modeline-package): New configurable. Non-nil (the + default) means update the Lisp package in the modeline using an + idle timer. + (slime-repl-send-input): Make the `slime-repl-old-input' property + cover the whole input (including newline) so that pressing RET on + the end of an input line works. + Use a unique integer as the value of this property to distinguish + adjacent inputs. + (slime-current-package): Deal with narrowing. + 2004-08-01 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * swank-allegro.lisp (swank-compile-string): Use a temporary file @@ -25,20 +53,6 @@ * swank-backend.lisp (sldb-condition): Show the original condition in the message. - -2004-07-30 Luke Gorrie <luke(a)bluetail.com> - - * slime.el (slime-choose-overlay-region): Tweaked the - multiline-annotation-avoidance code to work with forms not - starting with an open-paren, e.g. `(..) or #'(..). - (slime-update-modeline-package): New configurable. Non-nil (the - default) means update the Lisp package in the modeline using an - idle timer. - (slime-repl-send-input): Make the `slime-repl-old-input' property - cover the whole input (including newline) so that pressing RET on - the end of an input line works. - Use a unique integer as the value of this property to distinguish - adjacent inputs. 2004-07-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at>

1 0

[slime-devel] Package gets lost in narrowed buffer
by Alain.Picard＠memetrics.com 02 Aug '04

02 Aug '04

Dear Slimers, This might be a strange way of working, but I quite often "narrow" my lisp buffers, to work on only a few definitions. Recently, SLIME seems to lose track of the package in that situation and evaluates the C-cC-c requests in the USER package, instead of the correct package. Cheers,

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 01 Aug '04

01 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.492 slime/ChangeLog:1.493 --- slime/ChangeLog:1.492 Fri Jul 30 14:41:25 2004 +++ slime/ChangeLog Sat Jul 31 23:46:48 2004 @@ -1,3 +1,15 @@ +2004-08-01 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-allegro.lisp (swank-compile-string): Use a temporary file + and set excl::*source-pathname* manually. This way we can find + the source buffer of functions compiled with C-c C-c. + (call-with-temp-file, compile-from-temp-file): New functions. + (list-callers, function-callers, in-constants-p) + (map-function-constants): Implements list callers by groveling + through the constants pools of named functions. + + * swank-lispworks.lisp: Minor refactoring. + 2004-07-30 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-connection): Say "No default connection @@ -10,7 +22,10 @@ * swank-cmucl.lisp (call-with-debugging-environment): Only handle DI::UNHANDLED-CONDITION not all DI:DEBUG-CONDITIONs. - + + * swank-backend.lisp (sldb-condition): Show the original condition + in the message. + 2004-07-30 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-choose-overlay-region): Tweaked the

1 0