slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] "query-replace" strangeness.
by Iain Little 26 Jul '04

26 Jul '04

It seems that cvs slime is interfering with "query-replace" (also checked "replace-string"). (Using cmucl18e) As a simple example (putting file contents in triple-double-quotes): I start with: """ bug """ Then after doing a query-replace to replace "bug" with "buggy" I get: """ buggyug """ This only happens when slime is running. (It works fine both before slime starts up, and after quitting.) I have also noticed strange capitilisation of file contents in a way not at all related to the replace query on more complicated examples, but I couldn't. """ strange BUG """ Then doing query-replace "bug" with "buggy": """ sTRANGE BUGGYUG """ As a final twist, everything seems to work fine when the buffer has been modified since last being saved. This leads me to suspect that the problem is caused by the cache stuff, somehow... Iain

2 1

[slime-devel] Function signatures incomplete
by Iain Little 24 Jul '04

24 Jul '04

I noticed that in cvs slime the entire function signature (when typing a function/macro into a lisp-mode buffer) doesn't always get shown anymore; it seems to cut off after the first line. For example, the signature for MAKE-ARRAY cuts off after "(element-type t)" in cvs slime (cmucl18e). I checked with slime-1.0alpha, and it works as expected there. Cheers, Iain

1 0

[slime-devel] Emacs error when quitting Slime
by Ivan Boldyrev 24 Jul '04

24 Jul '04

Greetings! When I quit Slime with comma and 'quit', Emacs shows error message: error in process sentinel: Connection closed. Backtrace: Debugger entered--Lisp error: (error "Connection closed.") signal(error ("Connection closed.")) error("Connection closed.") (cond ((null conn) (error "Not connected.")) ((not ...) (error "Connection closed.")) (t conn)) (let ((conn ...)) (cond (... ...) (... ...) (t conn))) slime-connection() (eq (slime-connection) slime-default-connection) (and (slime-connected-p) (eq (slime-connection) slime-default-connection)) (if (and (slime-connected-p) (eq ... slime-default-connection)) (progn (setq slime-state-name name) (force-mode-line-update))) (when (and (slime-connected-p) (eq ... slime-default-connection)) (setq slime-state-name name) (force-mode-line-update)) slime-set-state("[not connected]") slime-net-sentinel(#<process SLIME Lisp> "exited abnormally with code 256\n") It is not fatal, but annoying. I tried to hack the code myself, but I still do not understand full code, so I am afraid to break something. -- Ivan Boldyrev Violets are red, Roses are blue. // I'm schizophrenic, And so am I.

3 5

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

24 Jul '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.485 slime/ChangeLog:1.486 --- slime/ChangeLog:1.485 Thu Jul 22 09:55:26 2004 +++ slime/ChangeLog Fri Jul 23 09:36:36 2004 @@ -1,3 +1,13 @@ +2004-07-23 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-set-state): Show the message in the modeline in + the case where we aren't connected. Otherwise the "not connected" + status is ignored. + (slime-net-sentinel): Close the connection before changing the + status message. The old behaviour of this combined with the old + behaviour of `slime-set-state' could generally cause spurious + errors after a connection was closed. + 2004-07-22 Luke Gorrie <luke(a)bluetail.com> * swank.lisp (carefully-find-package): Return *BUFFER-PACKAGE* if

1 0

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

23 Jul '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.483 slime/ChangeLog:1.485 --- slime/ChangeLog:1.483 Wed Jul 21 12:56:54 2004 +++ slime/ChangeLog Thu Jul 22 09:55:26 2004 @@ -1,3 +1,13 @@ +2004-07-22 Luke Gorrie <luke(a)bluetail.com> + + * swank.lisp (carefully-find-package): Return *BUFFER-PACKAGE* if + no other package can be found. This is reverting a previous change + that broke completion in buffers with no known package. + + * slime.el (slime-maybe-start-lisp): Check that *inferior-lisp* + exists /and/ has a running process. Fixes a startup problem if + your inferior-lisp has died and you want to restart SLIME. + 2004-07-21 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-sync-package-and-default-directory): Sync

1 0

[slime-devel] nightly build
by Jeff Bowman 22 Jul '04

22 Jul '04

I am behind a firewall that prevents cvs from coming in. I have downloaded the slime-1.0alpha.tar.gz file and am using it, but I noticed one of the problems I'm having is mentioned in the list as being fixed. So my question is: is there a nightly build mechanism in place where I can download a more current version of slime than the tarball, or is the tarball contents updated frequently so I can get the fix? [RE: Symbol Completion Broken (CLISP)] Thanks! This is a great tool! Jeff

2 1

[slime-devel] Symbol completion broken (CLISP)
by Steven E. Harris 22 Jul '04

22 Jul '04

Using CLISP with SLIME updated from CVS as of 21 June 2004, symbol completion coaxed by M-Tab (`slime-complete-symbol') no longer produces anything useful. If I type (with-o in a buffer in SLIME mode connected to a CLISP repl and hit M-Tab, SLIME reports in the minibuffer [Can't find completion for "with-o"] and refuses to either complete or suggest completions for the partial symbol. This used to work as of about two weeks ago, but I can't recall when the exact last time I tested this was. -- Steven E. Harris

2 2

[slime-devel] Uh, (require 'slime) errors out
by Peter Seibel 22 Jul '04

22 Jul '04

I can no longer (require 'slime) because I get an error "Not connected". I'm trying to track it down from the backtrace (see below) but since it just started happening I'm assuming this is due to some recent change and perhaps the author of said change will know right away what's wrong. -Peter P.S. I'm a CVS idiot--how do I see what changes have been made recently to a given file? P.P.S Here's the backtrace: Debugger entered--Lisp error: (error "Not connected.") signal(error ("Not connected.")) error("Not connected.") (cond ((null conn) (error "Not connected.")) ((not ...) (error "Connection closed.")) (t conn)) (let ((conn ...)) (cond (... ...) (... ...) (t conn))) slime-connection() (or process (slime-connection) (error "No connection")) (process-buffer (or process (slime-connection) (error "No connection"))) (set-buffer (process-buffer (or process ... ...))) (save-current-buffer (set-buffer (process-buffer ...)) slime-rex-continuations:connlocal) (with-current-buffer (process-buffer (or process ... ...)) slime-rex-continuations:connlocal) (slime-with-connection-buffer (process) slime-rex-continuations:connlocal) slime-rex-continuations() slime-busy-p() (null (slime-busy-p)) (and (not (sldb-get-default-buffer)) (null (slime-busy-p))) slime-at-top-level-p() (progn (slime-at-top-level-p)) (if (progn (slime-at-top-level-p)) (slime-print-check-ok check-name-14528) (cond (... ... ...) (t ... ...)) (when slime-test-debug-on-error (debug ...))) (let ((check-name-14528 "At the top level (no debugging or pending RPCs)")) (if (progn ...) (slime-print-check-ok check-name-14528) (cond ... ...) (when slime-test-debug-on-error ...))) (slime-check "At the top level (no debugging or pending RPCs)" (slime-at-top-level-p)) slime-check-top-level() eval-buffer(#<buffer *load*> nil "slime" nil t) load-with-code-conversion("/home/peter/cvs/slime/slime.el" "slime" nil t) require(slime) eval((require (quote slime))) eval-last-sexp-1(nil) eval-last-sexp(nil) call-interactively(eval-last-sexp) -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

5 5

[slime-devel] Slime cannot connect to ACL6.2 win32
by Thomas Schilling 22 Jul '04

22 Jul '04

The exact error message is: (stream/warning) failure to open network stream to host "localhost" for service "4005" Took a look at the changelog--Luke, something to confess? The relevant init.el part: ;; start up slime (global-set-key [(f5)] '(lambda () (interactive) (shell-command "c:/programme/acl62-demo/allegro-ansi.exe +B +cm -L ~/slime.lisp&") (sleep-for 3) (slime-connect "localhost" 4005) (cd "~/Eigene Dateien/"))) and ~/slime.lisp is: (load "~/Eigene Dateien/devel/lisp/slime/swank-loader.lisp") (swank::create-swank-server 4005 :spawn #'swank::simple-announce-function t) -- ,, \../ / <<< The LISP Effect |_\\ _==__ __ | |bb| | _________________________________________________

2 10

[slime-devel] can't restart lisp/slime in the same emacs session
by Chisheng Huang 22 Jul '04

22 Jul '04

After doing a cvs update today (2004-07-21 PDT), I'm having trouble restarting Lisp/Slime: 1. "M-x slime" to get a *slime-repl[1]* buffer 2. Type (quite) in *slime-repl[1]* buffer and this message shows up in the mini buffer: error in process sentinel: Connection closed 3. Doing "M-x slime" again will not get a *slime-repl[1]* buffer and the following message shows up in the mini buffer: No Lisp subprocess: see variable `inferior-lisp-buffer'. I hope I do not have to mess with inferior-lisp-buffer everytime I restart Lisp/Slime. I'm using CMUCL-19a-pre3 (x86, Linux) and GNU Emacs 21.2.1. Best, -cph

2 2

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