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

[slime-devel] clhs-lookup for reader macros
by Stas Boukarev 27 Feb '09

27 Feb '09

I added reader macros for hyperspec-lookup, hope this would be useful. -- With Best Regards, Stas.

2 1

[slime-devel] Problem with truncation of strings in debugger
by Jeff Workman 26 Feb '09

26 Feb '09

When I evaluate (format t "~A" (some-str-function)) on a longish string in debugger with E, the string is printed truncated, which seems like the wrong behavior to me. Also, surprisingly when I evaluate (setf *str* (some-str-function)) from debugger, the string stored in *str* is truncated as well. That suggests to me that the debugger is modifying the behavior of (format nil ...) or other functions I use in constructing strings used internally in my program, which would obviously be very bad and could interfere with operation of the program. I'm using SBCL 1.0.20 on Linux (and cvs slime) btw.

3 3

[slime-devel] Inspector doc
by Madhu 17 Jan '09

17 Jan '09

Helu, I'm having trouble using the inspector effectively: some objects are truncated, some lists are truncated etc. These boil down to bindings of printer variables [the debug state, etc] Can the inspector related variables be documented, and the rationale spelt out as to which output is being truncated, why, and under what circumstances? Could the hardcoded constants be documented as being hardcoded? I suspect this is not too much to ask if the new inspector is a "better thought out" replacement, the design could be explained in a few paragraphs in comments in the code or in a separate doc. I think it is an important enough component of SLIME to define the behaviour outside of the code which implements it. -- Madhu

4 8

[slime-devel] request for pecifying location fasl-files
by Knut Olav Bøhmer 10 Jan '09

10 Jan '09

Hi, I would like to be able to specify where slime should place it's fasl-files when running slime-compile-and-load-file. The location should be per-buffer/filename configurable by placing variable-definition in the header of a .lisp file or by a hook that runs when a .lisp file is opened. I have attached an example implementation that I use, and have used for a long time. It works for me. -- Free Software Consultant Cell: +47 - 47 34 40 08 Phone: +47 - 21 53 69 00, Fax: +47 - 21 53 69 09 Addr: Nydalsveien 30b, 0484 Oslo <http://www.freecode.no/>

5 4

[slime-devel] swank-listener-hooks fix, paredit-friendly REPL patch
by Ivan Shvedunov 12 Nov '08

12 Nov '08

Hello. I've discovered a problem with swank-listener-hooks (rendering REPL unusable), which is needed for CLG. The trivial patch that restores it's functionality is attached. Another patch attached to this message makes SLIME REPL usable in Paredit mode by using the part of input between its start and (point) as history search pattern. I've sent a patch doing that long time ago, it was applied but later accidentally (as I understood it after asking on #lisp) reverted. I forgot about it for a while and just kept changes in my copy of SLIME, but now I decided to share them again. Thanks. Ivan

4 10

[slime-devel] slime has broken cmucl mp
by Madhu 01 Nov '08

01 Nov '08

It used to be possible to run multiprocessing servers like a webserver which coexisted with slime. This is no longer possible With current CVS slime, swank's WAIT-FOR-EVENT blocks all other processes from handling FD events There is a simple test case, but here is a more realistic one: I'm attaching a program "t2.lisp" which seeks to illustrates the problem. This is a simple program which listens on a port [8128 by default] and prints a message to clients which connect to it. -- In a bare lisp * (load "t2.lisp") LISTEN-FOR-CONNECTIONS creates a process which listens at port 8128. -- run `telnet localhost 8128' from a shell, a few times. This will result in the bogus service printing a message to the telnet client, as expected. -- load slime in the lisp, and listen at port 4005 * (load "/path/to/swank-loader.lisp") * (swank-loader::init) * (swank::setup-server 4005 #'print nil nil (swank::find-external-format "latin-1-unix")) -- Connect to the lisp from emacs using M-x slime-connect localhost 4005 -- run `telnet localhost 8128' from a shell. This hangs until the slime connection exits. This is a serious problem, and exposes many issues with SLIME's design. -- Madhu

2 4

[slime-devel] q in sldb doesn't quit anymore
by Raymond Toy 01 Nov '08

01 Nov '08

In the latest CVS build of slime, pressing "q" in sldb doesn't abort anymore. I get another error. Pressing "a" does abort. I hope this wasn't an intentional change. I have "q" hardwired now, so changing to "a" will be hard. :-( Ray

2 2

[slime-devel] CVS Snapshot Link Broken
by Elliott Slaughter 31 Oct '08

31 Oct '08

Hi, The link to the CVS snapshot ( http://common-lisp.net/cgi-bin/viewcvs.cgi/root.tar.gz?root=slime&view=tar) gives me a 403 Forbidden error. It would be nice if this link worked, especially for Windows users who may not have CVS installed. Thanks. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

2 2

[slime-devel] sb-impl::indenting-streams on the chopping block
by Nikodemus Siivola 31 Oct '08

31 Oct '08

Aside from slime/contrib/swank-presentations.lisp (or (and (typep stream 'sb-impl::indenting-stream) (slime-stream-p (sb-impl::indenting-stream-stream stream))) (and (typep stream (find-symbol "PRETTY-STREAM" 'sb-pretty)) (find-symbol "ENQUEUE-ANNOTATION" 'sb-pretty) (not *use-dedicated-output-stream*) (slime-stream-p (sb-pretty::pretty-stream-target stream))))) SB-IMPL::INDENTING-STREAM is, as far as I can tell, otherwise unused. Does someone actually use them? Any objections to deleting them? (And the first leg of the OR in Slime.) Cheers, -- Nikodemus

2 2

[slime-devel] Auto-jumping to compiler notes
by Jeff Workman 31 Oct '08

31 Oct '08

I noticed that there seems to have been a recent change to SLIME that makes it jump to compiler notes automatically when a file is compiled. Also, it seems to jump even to SBCL compiler optimization notes, which makes it very annoying to work on files where I have speed declarations. I don't like the auto-jumping in general, since there are times I might have a warning in a file temporarily while working on something else in the file, and people can just run slime-next-note manually if they want to see the notes, but at a minimum it shouldn't apply to optimization notes. Or if you don't want to change the default behavior, is there a variable I can set to disable it?

2 1