slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] slime-echo-arglist-function & slime-autodoc-mode
by Ilya Perminov 11 Jun '09

11 Jun '09

Switching slime-autodoc-mode on or off in a buffer puts it info an inconsistent state in other buffers, because slime-autodoc-mode changes slime-echo-arglist-function that is not is a buffer-local variable. Thanks, Ilya

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 11 Jun '09

11 Jun '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1776 slime/ChangeLog:1.1779 --- slime/ChangeLog:1.1776 Thu May 28 15:01:09 2009 +++ slime/ChangeLog Thu Jun 4 05:08:06 2009 @@ -1,3 +1,13 @@ +2009-06-04 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-dispatch-event [:emcas-rex]): Don't clutter + the main code-path with confusing error handling. + +2009-06-04 Helmut Eller <heller(a)common-lisp.net> + + * swank-openmcl.lisp (*known-processes*, mailbox): Use a weak + hashtable to plug the memory leak. + 2009-05-28 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (def-slime-test): Forgot to remove debugging code.

2 3

[slime-devel] SBCL, Win32 and git SLIME
by Gleb Golubitsky 11 Jun '09

11 Jun '09

Hi All, 2 days ago i'd checkouted fresh SLIME from git repo (http://github.com/nablaone/slime.git) and found out that SLDB with SBCL@win32 is broken. The trouble was when you enter to sldb and choose any restart, the inferior-lisp completely hangs (when i try to evaluate something in REPL the only i got was the message "the command is queued"). I've hacked abit into the code and found a workaround for this problem: diff --git a/swank.lisp b/swank.lisp index b66af8a..35b879b 100644 --- a/swank.lisp +++ b/swank.lisp @@ -2534,6 +2534,7 @@ after Emacs causes a restart to be invoked." (handle-sldb-condition c)))))) (send-to-emacs `(:debug-return ,(current-thread-id) ,level ,*sldb-stepping-p*)) + #-(and sbcl win32) (wait-for-event `(:sldb-return ,(1+ level)) t) ; clean event-queue (when (> level 1) (send-event (current-thread) `(:sldb-return ,level))))) I'm not sure whether this "patch" breaks something else but it's working for me. WBR, Gleb Golubitsky

2 1

[slime-devel] [Patch] make slime-net-coding-system customizable
by Stas Boukarev 07 Jun '09

07 Jun '09

Here it is. -- With best regards, Stas.

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 06 Jun '09

06 Jun '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1779 slime/ChangeLog:1.1781 --- slime/ChangeLog:1.1779 Thu Jun 4 05:08:06 2009 +++ slime/ChangeLog Fri Jun 5 15:58:53 2009 @@ -1,3 +1,15 @@ +2009-06-05 Helmut Eller <heller(a)common-lisp.net> + + Don't clutter compiler messages with source positions. Especially + stuff like "In an anonymous lambda form inside an anonymous lambda + form inside an anonymous lambda form inside FOO: Undeclared free + variable X" is not helpful. + + * swank-openmcl.lisp (compiler-warning-short-message): New GF. + (handle-compiler-warning): Use it. + + (disassemble-frame): Print current PC. + 2009-06-04 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-dispatch-event [:emcas-rex]): Don't clutter

1 0

[slime-devel] Installing swank
by Patrick May 05 Jun '09

05 Jun '09

I'm having trouble installing swank locally. I had it working by adding a symbolic link from /usr/local/src/slime/swank.asd to /usr/ local/asdf-install/site-systems/swank.asd, but that required write access to /usr/local/src/slime for temporary files. Is there a way to specify a different directory for those? I then tried this: (make-package :swank-loader) (defparameter swank-loader::*source-directory* "/home/pjm/slime/") (defparameter swank-loader::*fasl-directory* "/home/pjm/slime/") (load "/home/pjm/slime/swank-loader.lisp") (setq swank:*use-dedicated-output-stream* nil) (swank:create-server :port 4005 :dont-close t) But it resulted in: > Error: Reader error on #<BASIC-FILE-CHARACTER-INPUT-STREAM ("/home/ pjm/ccl-init.lisp"/4 ISO-8859-1) #x300040F05A0D>, near position 714, within "etq swank:*use-dedic": > Reference to unknown package "SWANK". > While executing: CCL::SIGNAL-READER-ERROR, in process listener(1). Is there a way to install via asdf locally? (Clozure CL 64-bit on CentOS, if that matters.) Thanks, Patrick

3 3

[slime-devel] REPL problems
by Stephen Lee 05 Jun '09

05 Jun '09

I have manage to install SLIME (latest cvs), Emacs 22.3 and SBCL 1.0.22 on Windows. Managed to configure and start SLIME. But REPL is not working. after i entered the code and press enter the code dosen't seem to execute Example CL-USER>(+ 1 2) <enter> No 3 is displayed I set up SLIME on Ubuntu before and it works so is it a windows thing? I followed the instructions here http://common-lisp.net/pipermail/slime-devel/2008-May/007331.html _________________________________________________________________ NEW! Get Windows Live FREE. http://www.get.live.com/wl/all

5 11

[slime-devel] slime-disconnect kills remote ccl
by Patrick May 04 Jun '09

04 Jun '09

Hi, I started Clozure from the command line on a remote machine and loaded swank with (asdf:oos 'asdf:load-op :swank). Since I'd just updated to the CVS head for slime, it recompiled. I got these warnings: ; Warning: These Swank interfaces are unimplemented: ; (ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER CALLS- WHO ; FIND-SOURCE-LOCATION REMOVE-FD-HANDLERS REMOVE-SIGIO- HANDLERS SAVE-IMAGE ; SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN SLDB-STEP-INTO SLDB-STEP-NEXT ; SLDB-STEP-OUT) ; While executing: SWANK-BACKEND::WARN-UNIMPLEMENTED-INTERFACES, in process listener(1). NIL Are they important? I then started swank: ? (setq swank:*use-dedicated-output-stream* nil) NIL ? (swank:create-server :port 4005 :dont-close t) ;; Swank started at port: 4005. 4005 ? I set up an ssh tunnel for port 4005 and was able to connect and use the Clozure image from Emacs on my local box. When I was done I used M-x slime-disconnect and it killed the Clozure image with this error: ;; swank:close-connection: Unexpected end of file on #<BASIC-TTrace/ BPT trap Do I have something misconfigured? Thanks, Patrick

3 6

[slime-devel] What does swank do with streams?
by mikel evins 04 Jun '09

04 Jun '09

I realize the question in the subject line is not specific enough to elicit useful answers. I need to ask some questions about how swank uses streams, so that I can ensure that forthcoming changes to CCL coexist with swank in a civil fashion. Unfortunately, I don't know enough about swank to ask intelligent questions. Basically, what's happening is that we're working on some changes to CCL that are intended to make inspection and debugging of running Cocoa apps more reliable and convenient. In the course of that work, some of the Clozure hackers have noticed inputs and outputs going to unexpected places when swank servers are running. They're complaining about streams getting snatched out from under them. Doubtless this is because we don't properly understand what swank is doing with the streams. I frankly don't know how to frame an intelligent question on this subject, because I don't know enough about what swank is trying to accomplish and how it's going about it. So, what questions should I ask? My goal is to ensure that CCL controls the standard streams in a way it can rely on, while still allowing a swank server to be created and run. If you guys would help me zero in on the right questions to ask you about swank's operation, I'd appreciate it. -me

2 4

[slime-devel] Hints needed on why "Process inferior-lisp hangup" occurs
by Willem Rein Oudshoorn 02 Jun '09

02 Jun '09

I need some hints to start figuring out why I regularly get a "Process inferior-lisp hangup" in my *inferior-lisp* buffer, but I do not have clue where to start. Situation: * OS: Mac OS X * Lisp version: sbcl 64bit 1.0.28 and ccl 1.3-r12156M (64bit) * Slime version: CVS version as of today. "Reproduction Scenario" 1 Start slime with one of the two lisp implementaitons mentioned above 2 Open "/dev/tty.NXT-DevB-1", which is a serial blue tooth connection to a Lego NXT brick. 3 Turn of the Lego NXT brick (the other side of the serial connection) After this, I get the "Process inferior-lisp hangup" in the *inferior-lisp* buffer. In contrast, if I do not run this through slime, but just run it from a terminal the lisp implementaiton is not killed. I assume that the serial bluetooth connection is closed from the other side and that that somehow closes also the slime connection. But I don't know why, if this is normal, and how to change this behaviour. All hints are appreciated. Wim Oudshoorn.

3 5

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