slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] can't change *readtable* from repl
by Alan Ruttenberg 26 Mar '04

26 Mar '04

CL-USER> *readtable* #<READTABLE #x5322ECE> CL-USER> (copy-readtable) #<READTABLE #xD70F94E> CL-USER> (setq *readtable* *) #<READTABLE #xD70F94E> CL-USER> *readtable* #<READTABLE #x5322ECE> Noticed this because cl-interpol enabling function stopped working at some point. -Alan

2 2

[slime-devel] Re: [slime-cvs] CVS update: slime/HACKING
by Luke Gorrie 26 Mar '04

26 Mar '04

Helmut Eller <heller(a)common-lisp.net> writes: > +If you would like to send us improvements you can create a patch with > +C-x v = in the buffer or with 'diff -c'. You can also include a > +ChangeLog entry describing your change. Hey, I can't read 'diff -c'! But I'm willing to learn if you can cite some virtues :-)

5 5

[slime-devel] CVS broken: destructure-case failed
by Bjørn Nordbø 26 Mar '04

26 Mar '04

After updating to the current CVS version, I get the following error on slime-compile-defun. I have tried to find the error, but it seems to be in slime.el and I'm no good at elisp. - The error have probably been introduced in a patch during the last 24 hours or so. - It shows itself consistently on my setup; GNU Emacs 21.2.1, Lispworks 4.[13], Solaris. - Using the slime.el from yesterday (2004-03-25) works fine. This is the error message I get in Emacs: Compilation finished: 0 errors 0 warnings 0 notes [0.12 secs] error in process filter: cond: destructure-case failed: nil error in process filter: destructure-case failed: nil -- Lisp can accomodate a wide range of psychological problems.

2 1

[slime-devel] compile-log-show buffer
by Julian Stecklina 26 Mar '04

26 Mar '04

Hello, if I do (require 'slime) in XEmacs a *Compile-Log-Show* buffer opens. This is very annoying. At the moment I use (delete-other-window) in my init.el, but how can I find the real problem? Regards, -- Julian Stecklina Signed and encrypted mail welcome. Key-Server: pgp.mit.edu Key-ID: 0xD65B2AB5 FA38 DCD3 00EC 97B8 6DD8 D7CC 35D8 8D0E D65B 2AB5 Any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. - Greenspun's Tenth Rule of Programming

3 2

Re: [slime-devel] compile-log-show buffer
by Julian Stecklina 26 Mar '04

26 Mar '04

Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > Julian Stecklina <der_julian(a)web.de> writes: > >> if I do (require 'slime) in XEmacs a *Compile-Log-Show* buffer >> opens. This is very annoying. At the moment I use >> (delete-other-window) in my init.el, but how can I find the real >> problem? > > We byte-compile some functions when slime is loaded and some Emacs > versions display the log buffer. Not sure what the right fix is. We > could rewrite the functions so that they don't produce compiler > messages (might be difficult) or perhaps there are variables to > suppress the log buffer. Suggestions welcome. The strange thing is, that this log buffer is empty... Regards, -- Julian Stecklina Signed and encrypted mail welcome. Key-Server: pgp.mit.edu Key-ID: 0xD65B2AB5 FA38 DCD3 00EC 97B8 6DD8 D7CC 35D8 8D0E D65B 2AB5 Any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. - Greenspun's Tenth Rule of Programming

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 26 Mar '04

26 Mar '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.304 slime/ChangeLog:1.308 --- slime/ChangeLog:1.304 Wed Mar 24 07:51:27 2004 +++ slime/ChangeLog Thu Mar 25 19:48:04 2004 @@ -1,5 +1,28 @@ +2004-03-26 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-merge-notes-for-display): New function to merge + together compiler notes that refer to the same location. This is + an optimization for when there are a lot of compiler notes: + `slime-merge-note-into-overlay' concat'd messages together one by + one in O(n^2) time/space, and became noticeably slow in practice + with ~100 notes or more. + (slime-tree-insert): This function is now automatically + byte-compiled (good speed gain). + +2004-03-25 Bjørn Nordbø <bn(a)telenor.net> + + * swank-lispworks.lisp: (create-socket, set-sigint-handler) + (who-references, who-binds, who-sets): Add backward compatibility + for LW 4.1. + (dspec-buffer-position): Fix inappropriate use of etypecase. + 2004-03-24 Luke Gorrie <luke(a)bluetail.com> + * swank-sbcl.lisp (getpid): Use sb-posix:getpid. + + * slime.el (slime-inspector-mode-map): Added SPC as extra binding + for slime-inspector-next (like info-mode). + * doc/slime.texi: Added completion style and configuration. 2004-03-23 Alan Shutko <ats(a)acm.org> @@ -38,7 +61,7 @@ New functions. (with-connection): Fix quoting bug and move upwards before first use. - (send-output-to-emacs): Add kludge for SBCL !-package names. + (guess-package-from-string): Add kludge for SBCL !-package names. (apropos-list-for-emacs): Lispworks apparently returns duplicates; remove them. (inspect-object): Princ the label to allow strings and symbols.

1 0

Re: [slime-devel] possible bug in SLIME/Lispworks
by Bjørn Nordbø 25 Mar '04

25 Mar '04

Helmut Eller wrote: > Bjørn Nordbø <bn(a)telenor.net> writes: > > > > How do I set a breakpoint for SLDB in a source fragment (ie. what > > do I use instead of break)? > > You could use INVOKE-DEBUGGER, which hopefully doesn't rebind the > debugger hook :-). Alternatively you can add a method to > ENV-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER. E.g. you could add Another solution, I found, was to call (SWANK::SIMPLE-BREAK). As it is only used for debugging, I probably won't be condemned to heck for doing this.. However, I noticed your patch in the ChangeLog and now BREAK does what I want. Thank you very much! :-) > (defmethod env-internals:environment-display-notifier > (env &key restarts condition) > (swank::swank-debugger-hook condition nil)) > > to your ~/.swank.lisp. I added something like this in the CVS > version. It is also possible to override the Lispworks window > debugger by specializing the env argument. That is probably cool, but I wouldn't know as I have never used the Lispworks GUI environment. Bjørn

3 3

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 25 Mar '04

25 Mar '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.303 slime/ChangeLog:1.304 --- slime/ChangeLog:1.303 Tue Mar 23 16:38:48 2004 +++ slime/ChangeLog Wed Mar 24 07:51:27 2004 @@ -1,3 +1,7 @@ +2004-03-24 Luke Gorrie <luke(a)bluetail.com> + + * doc/slime.texi: Added completion style and configuration. + 2004-03-23 Alan Shutko <ats(a)acm.org> * swank-clisp.lisp (set-default-directory): New function.

1 0

[slime-devel] Manual labour
by Luke Gorrie 24 Mar '04

24 Mar '04

[Repost: I'm not sure that my via-Gmane post is getting through.] I've drafted a user manual in doc/slime.texi. It's also online at http://www.bluetail.com/~luke/misc/lisp/slime.ps.gz http://www.bluetail.com/~luke/misc/lisp/slime.pdf The PDF version is a bit ugly (from ps2pdf), because texi2pdf is choking on slime.texi for some reason. Feedback would be welcome, so please RTFM! Cheers, Luke

4 7

[slime-devel] Tab completion bug?
by Dirk Gerrits 24 Mar '04

24 Mar '04

Typing M, U, L, <TAB> in the SLIME REPL produces "multiple-value|-" where | represents the cursor/point. Is this a bug? If it'd produce "multiple-value-|" then "multiple-value-bind" and such would be just a tad easier to type. Regards, Dirk Gerrits

4 9

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