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

[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