slime-devel September 2008

slime-devel@common-lisp.net

27 participants
61 discussions

Start a nNew thread

[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] Saving *slime-scratch*
by Nikodemus Siivola 11 Oct '08

11 Oct '08

The attached patch associates *slime-scratch* with a file if you name one as "slime-scratch-file". I've been running slime with this a while, and rather like it. Something like this was talked about a while ago, and dropped because of what looked like an ideologinal objection to scratch-buffers in my mind. Is the consensus still against this? Cheers, -- Nikodemus Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.784 diff -u -r1.784 slime.el --- slime.el 16 Apr 2007 14:42:33 -0000 1.784 +++ slime.el 27 Apr 2007 13:26:17 -0000 @@ -4570,10 +4570,15 @@ (set-keymap-parent map lisp-mode-map) map)) +(defvar slime-scratch-file nil) + (defun slime-scratch-buffer () "Return the scratch buffer, create it if necessary." (or (get-buffer "*slime-scratch*") - (with-current-buffer (get-buffer-create "*slime-scratch*") + (with-current-buffer (if (not slime-scratch-file) + (get-buffer-create "*slime-scratch*") + (find-file slime-scratch-file)) + (rename-buffer "*slime-scratch*") (lisp-mode) (use-local-map slime-scratch-mode-map) (slime-mode t)

4 5

[slime-devel] default connections
by Stas Boukarev 03 Oct '08

03 Oct '08

It would be better for the remaining connection to become default when I quit the default one. -- With Best Regards, Stas.

6 18

[slime-devel] Finding source for methods
by jcm＠sdf.lonestar.org 02 Oct '08

02 Oct '08

Sorry if this was answered before, but the last 3 months of subject lines didn't seem to indicate the question was asked... When using M-. to find the source to a function, all is well. But for a *method*, is there a new binding to jump to the selected specialized method? It used to be possible to just hit SPC on the method, and would jump right to the code.

4 4

[slime-devel] UTF-8 support for slime in Lispworks back end
by Alain Picard 29 Sep '08

29 Sep '08

Dear Slimers, I've implemented support for Lispworks in slime so that all characters exchanged between emacs and lispworks are LW:SIMPLE-TEXT-STRING (vectors of LW:SIMPLE-CHAR) which allow one to directly send and receive korean, japanese etc characters from the REPL, and to hit C-c C-c on a utf-8 encoded file w/o blowing up the slime connection. Example transcript: XOS> (ui:caption 'are-you-sure-to-proceed) "계속 하시겠습니까?" XOS> (type-of *) LISPWORKS:SIMPLE-TEXT-STRING Limitations: * You MUST have set your lispworks to use LW:SIMPLE-CHAR by default. (see LW:SET-DEFAULT-CHARACTER-ELEMENT-TYPE) For us, this is done at time of delivery for the text console that we use to connect slime to. * You MUST be in an image where a recent FLEXI-STREAMS is loaded (i.e. :FLEXI-STREAMS must be on the features list.) Failure to satisfy this reverts you to the previous, broken behaviour. :-) * Only 1 type of connection to lispworks is allowed; i.e. you can't have one latin-1 and one utf-8 connection simultaneously. This is because I couldn't find out how to inspect the current connection to determine what external-format it had been opened with. Maybe somebody can fix this. * You can then set your emacs with this (setq slime-net-coding-system 'utf-8-unix) and have a UTF-8 interaction with lispworks. This patch is taken against a (very recent) tip checkout, and should apply cleanly, I hope. Cheers! Alain Picard -- Please read about why Top Posting is evil at: http://en.wikipedia.org/wiki/Top-posting and http://www.dickalba.demon.co.uk/usenet/guide/faq_topp.html Please read about why HTML in email is evil at: http://www.birdhouse.org/etc/evilmail.html

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 29 Sep '08

29 Sep '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1545 slime/ChangeLog:1.1547 --- slime/ChangeLog:1.1545 Fri Sep 26 19:14:10 2008 +++ slime/ChangeLog Sun Sep 28 08:14:44 2008 @@ -1,3 +1,21 @@ +2008-09-28 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-list-compiler-notes): Revert change from + 2008-08-15 which introduced automatic shrinkage of the + compiler-notes buffer. This turned out to be more annoying than + worthwhile. On the cases where it's desired, the user can just use + `C-x -' himself to shrink the notes buffer. + +2008-09-28 Helmut Eller <heller(a)common-lisp.net> + + Stop handling events in worker threads after sldb-quit. + + * swank.lisp (with-top-level-restart): New macro. + (handle-requests, spawn-worker-thread): Use it. + (process-requests): Drop the just-one argument. + (handle-or-process-requests): Deleted. Call handle-requests + directly. + 2008-09-27 Tobias C. Rittweiler <tcr(a)freebits.de> Improve ECL's arglist support somewhat.

1 0

[slime-devel] Wrong output positioning in the REPL
by Tobias C. Rittweiler 28 Sep '08

28 Sep '08

With the recent REPL overhaul, positioning of output and the REPL result is a bit screwed. For example, type 'foo at the REPL, then compile some form using C-c C-c, the REPL will look like ; compiling (DEFUN ASDFO ...)FOO So there's a newline missing. -T.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel September 2008