slime-devel July 2004

slime-devel@common-lisp.net

49 participants
82 discussions

[slime-devel] comma shortcut doesn't work always
by Edi Weitz 31 Jan '06

31 Jan '06

Another minor glitch that I encountered is that the comma shortcut in the REPL doesn't always work. I can consistently reproduce it (GNU Emacs 21.3.50 and also 21.3 release) like this: 1. Make sure point is at the beginning of a REPL input line. 2. Split Emacs frame into two windows, one of them being the REPL the other one containing something else. 3. Hide REPL window with C-x 0. 4. Now type M-x slime. 5. Type the comma. At this point I'm not asked for a shortcut command in the minibuffer but the comma is simply entered into the REPL instead. Anybody else seeing this? Cheers, Edi.

10 25

Re: [slime-devel] Re: CLISP SLIME implementation breaks in CVS
by Bill_Clementson＠peoplesoft.com 21 Jan '06

21 Jan '06

Luke Gorrie <luke(a)bluetail.com> writes: > Bill_Clementson(a)peoplesoft.com writes: > > > My previous SLIME installation was a CVS install from 4/18. I've just taken > > the latest CVS install and the CLISP SLIME implementation (under Windows) > > breaks. Here is the error: > > > > COERCE: #<MACRO #<COMPILED-CLOSURE SWANK::DEFSLIMEFUN>> cannot be coerced > > to type FUNCTION > > [Condition of type SIMPLE-TYPE-ERROR] > > I can reproduce this but I've no idea what is causing it. It /looks/ > like someone is trying to call defslimefun as a function rather than a > macro, but I don't see where it could happen -- the macro is declared > at the top of the only file that refers to it. > > I did fix a different but similar problem that I got under CLISP. It > seems like I had to swap the order of a couple of macros, one of which > expanded into into code that calls the other, but that surely can't be > the reason. > > > Backtrace: > > 0: EVAL frame for form (SWANK:CREATE-SWANK-SERVER 4007) > > Mine actually gives an empty backtrace (!). I fixed the Elisp-side to > handle that incase it helps someone more CLISP-savvy find the problem. Has anybody had any luck in finding the source of this problem? CLISP still breaks for me in the latest CVS. I have had a look at all of the DEFSLIMEFUN's that were modified since 4/18 (the previous CVS version that I had which was working ok with CLISP) and haven't found any obvious clues. Any suggestions on how I might debug this issue as it occurs at startup during the slime-connect processing in Emacs (after CLISP has started up successfully)? - Bill

5 6

[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] 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] 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] Did someone say they were working on a GF browser?
by Peter Seibel 31 Jul '04

31 Jul '04

I don't know if I saw it here, on c.l.l., or in my dreams but I seem to recall someone saying they were working on adding a generic function/method browser to SLIME. I.e. something by which you could see all the methods defined on a gf and then remove particular ones easily, etc. If so, how's it coming along? -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

6 15

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

31 Jul '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.490 slime/ChangeLog:1.492 --- slime/ChangeLog:1.490 Thu Jul 29 20:48:36 2004 +++ slime/ChangeLog Fri Jul 30 14:41:25 2004 @@ -1,3 +1,16 @@ +2004-07-30 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-connection): Say "No default connection + selected" if there are open connections but no default connection. + (slime-tree-indent-item): Point wasn't updated correctly if the + last line was empty. Use insert-before-markers instead of insert + to do it properly. + (slime-draw-connection-list): Don't break if there is no default + connection. + + * swank-cmucl.lisp (call-with-debugging-environment): Only handle + DI::UNHANDLED-CONDITION not all DI:DEBUG-CONDITIONs. + 2004-07-30 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-choose-overlay-region): Tweaked the

1 0

[slime-devel] Compilation Problem with CVS-Slime
by R. Mattes 30 Jul '04

30 Jul '04

Hello everyone, i just checked out the latest CVS version of Slime, but when i try to load it in emacs (21.3.1) i get the following error: debugger invoked on a SIMPLE-ERROR in thread 17146: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION SWANK-BACKEND:SPAWN (0)> when called with arguments (# :NAME "Swank"). You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT ] Reduce debugger level (leaving debugger, returning to toplevel). 1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop. ((NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION SWANK-BACKEND:SPAWN (0)> (#<FUNCTION "CLOSURE" {94EE2CD}> :NAME "Swank")) Any idea what's going wrong here? TIA Ralf Mattes

2 1

[slime-devel] no package name on a mode line after 2004-07-19?
by Chisheng Huang 30 Jul '04

30 Jul '04

Slime retrieved from CVS on or before 2004-07-19 would print a package name on the mode line of a buffer editing a Lisp file. After 2004-07-19, Slime stops printing a package name on a mode line. Is this change intentional? It's not documented in the change log. Printing a package name on a mode line is quite useful. Best, -cph

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel July 2004