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

[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] M-p/M-n doesn't move to the note in cvs slime and xemacs
by Raymond Toy 05 Jul '05

05 Jul '05

After updating slime to the CVS slime version of 2005-05-16 to get the GC message changes, I notice that M-p/M-n no longer seems to move the the previous/next compiler note when in the Lisp buffer. The compiler notes seem to be highlighted correctly, but M-p/M-n always say no next note. This is with cmucl 2005-05 snapshot, and xemacs 21.5-b20. This combination with slime from Feb or so was working just fine. I can look into this if someone gives a few pointers on where to look. Thanks, Ray

4 11

[slime-devel] Comment indentation in newer Emacsen
by Edi Weitz 03 Jul '05

03 Jul '05

Dumb question number two for today: I've recently switched to a CVS build (circa end of January) of GNU Emacs on Windows. Now, if I have a function like this in a lisp mode buffer (defun foo () "This is a very very very very very very very very very very very very long comment line." (bar x)) and press M-q within the comment string the result looks like so: (defun foo () "This is a very very very very very very very very very very very very long comment line." (bar x)) However, in 21.3 the result looked like this (defun foo () "This is a very very very very very very very very very very very very long comment line." (bar x)) which is what I prefer. Is this a bug or can the behaviour be changed with some setting that I'm missing? Thanks, Edi.

3 3

[slime-devel] SLIME supporting Corman Lisp 2.51
by Espen Wiborg 02 Jun '05

02 Jun '05

After much sweat and cursing, I now have SLIME working on Corman Lisp (only tested on 2.51). I've attached the necessary swank-corman.lisp as well as a patch against CVS HEAD. I actually had this working back in December, but due to a lack of round tuits I haven't made it official before. Scissored from swank-corman.lisp: ;;; Notes ;;; ===== ;;; You will need CCL 2.51, and you will *definitely* need to patch ;;; CCL with the patches at ;;; http://www.grumblesmurf.org/lisp/corman-patches, otherwise SLIME ;;; will blow up in your face. You should also follow the ;;; instructions on http://www.grumblesmurf.org/lisp/corman-slime. ;;; ;;; The only communication style currently supported is NIL. ;;; ;;; Starting CCL inside emacs (with M-x slime) seems to work for me ;;; with Corman Lisp 2.51, but I have seen random failures with 2.5 ;;; (sometimes it works, other times it hangs on start or hangs when ;;; initializing WinSock) - starting CCL externally and using M-x ;;; slime-connect always works fine. ;;; ;;; Sometimes CCL gets confused and starts giving you random memory ;;; access violation errors on startup; if this happens, try dumping a ;;; new image. ;;; -- Espen Wiborg <espenhw(a)grumblesmurf.org> The Unix philosophy: Make your program do one thing, and do it well.

5 14

[slime-devel] LOAD-SYSTEM and stealing file locks
by Peter Seibel 01 Jun '05

01 Jun '05

I've recently noticed that when I do a ,load-system and Emacs offers to save modified files, it complains about the files being locked by another process and asking if I want to steal the lock etc. However the PID it gives is in fact my Emacs process. So I wonder if SLIME is doing something funny under the covers--I can't imagine what but I finally correlated this with usin ,load-system so I'm hoping someone here might just know what's going on. -Peter -- Peter Seibel peter(a)gigamonkeys.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

4 3

[slime-devel] Additional source location information for SBCL
by Nikodemus Siivola 01 Jun '05

01 Jun '05

Development environments such as Slime benefit from being able attach additional source location information (eg. buffer associations) to functions. Currently Slime does this by patching SBCL in order to be able to attach its own plists to SB-C::DEBUG-SOURCE structures. I propose we add :SOURCE-PLIST option to WITH-COMPILATION-UNIT, with the following tentative spec: :SOURCE-PLIST Plist-Form Attaches the value returned by the Plist-Form to internal source location information of functions and definitions compiled in within the dynamic contour. Primarily for use by development environments, in order to eg. associate function definitions with editor-buffers. Can be accessed as SB-INTROSPECT:DEFINITION-SOURCE-PLIST. If multiple, nested WITH-COMPILATION-UNITs provide :SOURCE-PLISTs, they are appended togather, innermost left, unless :OVERRIDE is true, in which case previous :SOURCE-PLISTs are ignored. The space-costs of this are nominal: size of DEBUG-SOURCE structures is increased by one slot/word, but there is only one of those per compiled file -- though one per function loaded from source or entered at the toplevel. I think calling it a :SOURCE-PLIST is a reasonable compromise between more abstract names such as :INFO, the documentary nature of the -PLIST vrt. the appending behaviour, by YMMW. To illustrate the usage, the significant part of SWANK-COMPILE-STRING[*] could eg. become (with-compilation-unit (:source-plist (list 'emacs-buffer buffer 'emacs-string string 'emacs-position position)) (with-input-from-string (s string) (load s)))))) I've the SBCL parts of this implemented in my local tree, and most of swank-sbcl adapted for this. The questions to SBCL and Slime folks respectively: 1. Does the interface seem sane and something we would be happy to support? Are the non-slime use cases this doesn't reasonably cover? 2. Does this fit the needs of Slime? If this existed on other platforms as well, would you be tempted to use this instead of whatever you currently use? [*] To nitpick, I venture the opinion that SWANK-COMPILE-STRING is a misnomer, as as far as I can tell the intention is something like "evaluate the forms contained in this string as if they had been entered at the toplevel, but making sure all functions are compiled". Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs."

2 3

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 31 May '05

31 May '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.699 slime/ChangeLog:1.700 --- slime/ChangeLog:1.699 Tue May 24 21:10:08 2005 +++ slime/ChangeLog Tue May 31 20:38:58 2005 @@ -1,3 +1,14 @@ +2005-05-27 Espen Wiborg <espenhw(a)grumblesmurf.org> + + * swank-corman.lisp: New file, swank for Corman Lisp. + + * swank.lisp (simple-announce-function): force-output after + announcing. + (symbol-external-p): Be extra paranoid about the symbol's package; + find-symbol barfs on a nil package in Corman Lisp. + + * swank-loader.lisp: Add Corman Lisp support. + 2005-05-24 Alan Ruttenberg <alanr-l(a)mumble.net> * slime.el text-property-default-nonsticky not defined in @@ -178,6 +189,7 @@ slime-complete-symbol* and slime-simple-complete-symbol. 2005-05-06 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-openmcl.lisp specializer-name didn't handle structure-class which caused meta-. of methods specialized on defstruct arguments to fail.

1 0

[slime-devel] updating slime during idle time
by Chris Baker 29 May '05

29 May '05

Hi Slimers, I've recently started running slime with clisp on windows. This works great for most things, but now I'm starting to do windows gui programming, and windows wants each program to have it's own event loop, which interferes with slime, which has its own server update loop. Unfortunately, clisp is single threaded, so I can only update windows events or update slime requests at a given time. Is there a function I can call periodically to process slime requests at idle time? Or alternately, can I add a hook to swank so I can pump windows events when slime isn't processing anything? Many thanks for this great piece of software, and thanks in advance for any help anyone can provide. cbb -- 19:45:04 up 9 days, 21:54, 4 users, load average: 0.55, 0.27, 0.10

2 2

[slime-devel] Way to jump into file to error location?
by Jeffrey Cunningham 27 May '05

27 May '05

Hi, When I compile a buffer I often get an error message like this: -+ Errors (1) `-- Read error in form starting at 3192: ";; (list `(:p :class "small"" End-of-File on #<Stream for file "/home/jcunningham/code/lisp/html/test.lisp"> [+] Notes (2) My question is: is there a way (key-code maybe?) to find that start point in the file? Is there some way to get at least a line number? I've looked through some of the documents and googled a bit but haven't come up with anything yet. That number must be useful for something beyond counting characters from the beginning. ;-) --jeff cunningham

2 2