slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Daily ChangeLog diff
by Helmut Eller 23 Nov '08

23 Nov '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1586 slime/ChangeLog:1.1587 --- slime/ChangeLog:1.1586 Sat Nov 22 22:36:40 2008 +++ slime/ChangeLog Sun Nov 23 22:11:36 2008 @@ -1,3 +1,18 @@ +2008-11-23 Helmut Eller <heller(a)common-lisp.net> + + `q' in temp buffers should only delete the window if it was newly + created for the buffer. + + * slime.el (slime-display-popup-buffer): New function. Recognize + if the window didn't exist before. Save the created window and + the selected window in buffer local variables. + (slime-make-popup-buffer): Renamed from slime-popup-buffer. + (slime-popup-buffer-quit): Delete the created window (if needed) + and restore the old selected window. Don't touch other windows. + + (slime-edit-value-callback): Calling lisp-mode deletes all local + variables. We need to that inside with-popup-buffer. + 2008-11-22 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-update-all-modelines): Only walk through

1 0

[slime-devel] Highlighting of forms from sldb?
by Raymond Toy 23 Nov '08

23 Nov '08

I think this changed some time ago, but I didn't reported it. When I'm in sldb and press "v" on one of the stack frames, slime brings up the source file quite nicely in another window. Previously (with xemacs), the offending form would be highlighted, with the cursor in the sldb buffer. Now, what happens is that the offending form is very momentarily highlighted (in blue). Is my memory wrong, or has this changed? In any case, it's certainly much nicer if the form were highlighted, even if the cursor is in the sldb window. Ray

3 4

[slime-devel] 'q' in temporary buffer closes the window rather than returning to REPL
by Brett Hoerner 23 Nov '08

23 Nov '08

The documentation says, "Temporary buffers can be dismissed by pressing q. This kills the buffer and restores the window configuration as it was before the buffer was displayed." Using emacs 22.3.1 (or the latest Aquamacs or CarbonEmacs) and a CVS checkout of SLIME (current) when I (for example) open documentation with C-c C-d C-d and press 'q', it closes the whole window. I expect (based on the documentation above) that it should actually kill that buffer, show the REPL again, and put my cursor/focus back in my main window where I started, correct? Is there anything I could have set wrong, or somewhere I should look to debug this, if so? It would save me so much time if I didn't have to kill buffer and change windows after each little lookup, etc. It should be noted that I am using Clojure with swank-clojure, if that has any affect. I imagine that SLIME is what handles the interface though. Thanks! Brett

5 8

[slime-devel] Daily ChangeLog diff
by Helmut Eller 22 Nov '08

22 Nov '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1581 slime/ChangeLog:1.1586 --- slime/ChangeLog:1.1581 Sun Nov 2 12:05:24 2008 +++ slime/ChangeLog Sat Nov 22 22:36:40 2008 @@ -1,3 +1,40 @@ +2008-11-22 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-update-all-modelines): Only walk through + widnow-list not buffer-list. + (slime-restart-or-init-modeline-update-timer): Inrease the timer + interval to 0.5 seconds. + +2008-11-22 Gábor Melis <mega(a)retes.hu> + + Reincarnate "eval..." (almost) + + * slime.el (slime-compute-modeline-connection-state): Return the + number of outstanding requests if connected. + (slime-update-all-modelines): Renamed from slime-update-modelines, + loops through all slime buffers. + (slime-restart-or-init-modeline-update-timer): New function. + (slime-dispatch-event): Arrange for modelines to be updated on + :EMACS-REX and :RETURN. + +2008-11-22 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (invoke-default-debugger): New condition type. + (swank-debugger-hook): Handle invoke-default-debugger conditions. + (sldb-break-with-default-debugger): Signal invoke-default-debugger + to transfer control to the default debugger. + New argument DONT-UNWIND to invoke the native debugger without + unwinding the stack. + * slime.el (sldb-break-with-default-debugger): By default, + unwind the stack before invoke the native debugger. + With prefix argument, run the native debugger in the + dynamic environment of SLDB. + +2008-11-02 Helmut Eller <heller(a)common-lisp.net> + + * slime.el ([test] package-updating): Allegro returns "||" as + prompt for the keyword package. I guess that's acceptable. + 2008-11-02 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-popup-buffer-quit): Always delete windows and Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.140 slime/contrib/ChangeLog:1.141 --- slime/contrib/ChangeLog:1.140 Fri Oct 31 13:52:16 2008 +++ slime/contrib/ChangeLog Sat Nov 22 12:19:26 2008 @@ -1,3 +1,9 @@ +2008-11-22 Geoff Wozniak <geoff(a)wozniak.ca> + + * swank-c-p-c.lisp (parse-completion-arguments): Change the + package identifier from the string "KEYWORD" to the + form (symbol-name :keyword) for ACL's "modern" mode. + 2008-10-31 Nikodemus Siivola <nikodemus(a)random-state.net> * swank-presentation-streams.liso (slime-stream-p): delete

1 0

[slime-devel] is there a way to suppress polling in the minibuffer?
by Robert Solovay 22 Nov '08

22 Nov '08

When I run SLIME there is a constant transmission of the message "Polling /tmp/slime ... Is there a way to keep the polling but stop the constant minibuffer notifications? Thanks, --Bob Solovay

2 1

[slime-devel] Implementation Specific Configuration
by Volkan YAZICI 22 Nov '08

22 Nov '08

Hi, How can set local environment variables in slime-mode specific to each lisp implementation? I tried to use something similar to below code snippet. (defun custom-slime-mode () (interactive) ... ;; Implementation specific symbol completion. (setq slime-complete-symbol-function (case slime-lisp-implementation-name ((x y z) 'slime-simple-complete-symbol) (t 'slime-fuzzy-complete-symbol)))) (add-to-list 'slime-mode-hook 'custom-slime-mode) But emacs complains that (void-variable slime-lisp-implementation-name) How do you define implementation specific local environment variables? Regards.

2 2

[slime-devel] Fuzzy completion patch
by Geoff Wozniak 22 Nov '08

22 Nov '08

When using fuzzy completion with ACL's "modern" lisp (mlisp), completion of symbols in the keyword package fails. This small fix corrects that by changing the package identifier from the string "KEYWORD" to the form (symbol-name :keyword) in swank-c-p-c.lisp. -- Geoff

2 1

[slime-devel] Using SLIME with :sb-thread enabled in SBCL?
by Benjamin Lambert 20 Nov '08

20 Nov '08

Dear SLIME, I've been having this problem, in one way or another, for a long time now. But, I think, I'd always found some combination of SLIME and SBCL that worked together. Now, I'm stuck. I'm running SBCL 1.0.22, on Linux x86-64. I believe I have a very recent version of SLIME, checked out from CVS within the last few weeks. SLIME seems to work fine with the SBCL binary distribution. But, when I recompile it with ":sb-thread" enabled, Slime won't start. So, it seems that the threading is interfering with SLIME? When I starts Slime, this is the error I see see this in mini-buffer: List connection closed unexpectedly: exited abnormally with code 256 And, in the *inferior-lisp* buffer I see: " Implicitly creating new generic function STREAM-READ-CHAR-WILL- HANG-P. ; loading #P"/home/benlambert/.slime/fasl/2008-11-02/sbcl-1.0.22-linux- x86-64/swank.fasl" WARNING: These Swank interfaces are unimplemented: (CALLS-WHO DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-SPECIALIZES) ;; Swank started at port: 41099. 41099 * Process inferior-lisp hangup" I'm glad to provide any more debugging information that I can. Is there any fix, or workaround, that I could try? That is, short of just not using threading. Thanks for any help you might be able to give. Ben Lambert P.S. I'm a long time user and a big fan of Slime. Good work, all. -- Benjamin Lambert Graduate Student of Computer Science Carnegie Mellon University www.cs.cmu.edu/~belamber Mobile: 617-869-1844

2 1

[slime-devel] help: swank + acl81_express refuses to start in CVS emacs
by Madhu 19 Nov '08

19 Nov '08

I noticed this problem only in emacs 23.0.60 (not 22.1) and allegro express 8.1 on linux: ,---- | emacs -Q -eval '(add-to-list (quote load-path) "~/path/to/slime")' -eval '(require (quote slime))' | C-u M-x slime /path/to/acl_express/alisp `---- ,---- In the *inferior-lisp* buffer: | (progn (load "~/path/to/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/tmp/slime.12688" :coding-system "iso-latin-1-unix")) | | International Allegro CL Free Express Edition | 8.1 (Linux (x86)) (Jun 29, 2008 13:34) | Copyright (C) 1985-2007, Franz Inc., Oakland, CA, USA. All Rights | Reserved. | | [snip] | | ;; Swank started at port: 40835. | 40835 | CL-USER(2): CL-USER(2): | | ;; swank:close-connection: eof encountered on stream | #<MULTIVALENT stream socket connected from | localhost/40835 to localhost/46300 @ | #x7158daaa> `---- Allegro drops the connection as soon as emacs connects. ,---- And in Emacs: | Debugger entered: (("Error in timer" slime-attempt-connection (#<process inferior-lisp> nil 2) (file-error "make client process failed" "connection refused" :name "SLIME Lisp" :buffer nil :host "127.0.0.1" :service 56408))) | (condition-case data (apply fun args) (error (debug nil ...))) | slime-timer-call(slime-attempt-connection #<process inferior-lisp> nil 2) | apply(slime-timer-call (slime-attempt-connection #<process inferior-lisp> nil 2)) | byte-code("[snip]" [timer apply 5 6] 4) | timer-event-handler([t 18720 56375 253953 0.3 slime-timer-call (slime-attempt-connection #<process inferior-lisp> nil 2) nil]) `---- [The probem persists after updating patches for ACL (including the aug 27 base patch). The problem was not observed in the ACL 8.1 release from 2007 (but as that distribution is unavailable, I am not able to check).] The calls at allegro probably looks like: (ERROR END-OF-FILE :STREAM ...) ((:EFFT DC-READ-CHAR :LATIN1-BASE) :UNKNOWN :UNKNOWN ...) (SWANK::DECODE-MESSAGE #<MULTIVALENT stream socket connected from localhost/43977 to localhost/55570 @ #x7158963a>) I've ensured consistent coding systems between emacs and slime, I am stumped at finding a workaround, so I am soliciting suggestions -- Madhu

2 3

[slime-devel] parsing of local functions & macros
by Tamas K Papp 15 Nov '08

15 Nov '08

Hi, I find SLIME's ability to display argument syntax in the status bar and complete function names and argument lists very useful. I am just wondering it if would be possible to make this work for local functions and macros too. Eg when I write (flet ((strange-function (a b) (+ a b (* a b)))) (strng-f then C-c C-i could offer the completion strange-function among the choices, then its arguments would display in the status bar, and C-c C-s would complete them. Same for macrolet. I know very little about SLIME's internal workings. Is it possible to do this? Thank you, Tamas

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel