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

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 28 Sep '05

28 Sep '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.788 slime/ChangeLog:1.789 --- slime/ChangeLog:1.788 Thu Sep 22 22:27:04 2005 +++ slime/ChangeLog Wed Sep 28 00:17:50 2005 @@ -1,3 +1,33 @@ +2005-09-28 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-multiprocessing): Deleted. No longer needed. + (slime-init-command): Updated accordingly. + (slime-current-package): Add a special case for Scheme. + (slime-simple-completions, slime-apropos): Quote the package, + because in can be a plain symbol in Scheme. + (slime-inspector-reinspect): Use a proper defslimefun. + + * swank.lisp (inspector-reinspect): New function. + (start-server): Call initialize-multiprocessing before starting + the server and startup-idle-and-top-level-loops afterwards. + Calling startup-idle-and-top-level-loops here shouldn't be a + problem because start-server is only invoked at startup via stdin. + + * swank-scheme48/source-location.scm: New file. For M-. + * swank-scheme48/module.scm (list-all-package): New function. + * swank-scheme48/interfaces.scm (module-control-interface): Export it. + * swank-scheme48/inspector.scm: Add methods for records and and + hashtables. + (swank:arglist-for-echo-area): Implement it. Only works for + functions with enough debug-data (ie. only user-defined functions). + * swank-scheme48/completion.scm: New file. + (swank:simple-completions, swank:apropos-list-for-emacs): Implemented. + * swank-scheme48/load.scm, swank-scheme48/defrectypeX.scm: Renamed + the file from defrectype*.scm + * swank-scheme48/packages.scm (swank-general-rpc): Don't use + posix-process because it doesn't work on Windows, and we don't need + it for a mulithreaded server. + 2005-09-22 Helmut Eller <heller(a)common-lisp.net> * swank-backend.lisp (*gray-stream-symbols*): Collect the needed

1 0

[slime-devel] Re: SLIME48: a Swank back end in Scheme48
by Hoehle, Joerg-Cyril 28 Sep '05

28 Sep '05

Hi, Taylor Campbell wrote: >To clarify briefly: by a fork of SLIME for SLIME48, I don't mean to >make a fork that is completely oriented toward Scheme48 (or Scheme48 & >MIT Scheme, or whatever), but rather to make a more clearly specified >network protocol for communicating between a user interface and a Lisp >system [...] I'm always in favour of clearing up protocols, but I wonder why a fork is needed for that and what it has to do with Scheme? To me it's just 2 completely different things. As far as my use of Scheme goes, I've used M-x run-lisp (the old cmulisp.el) when using Kawa in the past and hope that the original run-lisp.el still works with SLIME (I haven't tested that), i.e. that SLIME for CL and run-lisp can coexist in the same Emacs, since I sometimes use both CL and Scheme at the same time. BTW, cmuscheme.el does IMHO not provide as much functionality as cmulisp/run-lisp.el, except for Scheme-style pretty printing. I'd be happy if a single download of a SLIME package would allow me to work with both CL and a Scheme (Kawa?) and whatever, instead of trying to figure out how to get two forks with likely .el files with equal names to work in the same Emacs. Regards, Jorg Hohle.

1 0

RE: [slime-devel] Re: Persistent REPL history
by Emre Sevinc 28 Sep '05

28 Sep '05

-----Original Message----- From: slime-devel-bounces(a)common-lisp.net on behalf of Marco Baringer Sent: Wed 9/28/2005 10:26 AM To: slime-devel(a)common-lisp.net Subject: [slime-devel] Re: Persistent REPL history Stefan Kamphausen <skampi(a)gmx.net> writes: >> That would be fine if the connection is always local. What would >> happen to a history with a REPL that is connected to a remote lisp? >> Write to local disc or pass it to the remote machine. If the latter >> it *might* be a performance problem. I can't tell because only work >> locally for the moment. > >personally i'd much prefer the history be saved locally, i don't want >to have production machines with development files lying around. >my 0.02EUR I really would like to see a persistent REPL history in SLIME. Cool idea :) Is there any plan to put that feature into the offical codebase? I'm getting impatient to try it ;-) Happy hacking, -- Emre Sevinc

2 1

[slime-devel] defrectype*.scm is an illegal filename for Windows
by Glenn Ehrlich 27 Sep '05

27 Sep '05

To the scheme folks, defrectype*.scm is an illegal filename for Windows (you can't have '*' in a filename). This has popped up within the last week or so in the cvs version. Glenn

2 1

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 22 Sep '05

22 Sep '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.787 slime/ChangeLog:1.788 --- slime/ChangeLog:1.787 Wed Sep 21 22:55:50 2005 +++ slime/ChangeLog Thu Sep 22 22:27:04 2005 @@ -1,3 +1,22 @@ +2005-09-22 Helmut Eller <heller(a)common-lisp.net> + + * swank-backend.lisp (*gray-stream-symbols*): Collect the needed + symbols here, so that we don't need to mention them in every + backend. + (import-from). New function. + + * swank-sbcl.lisp, swank-allegro.lisp, swank-lispworks.lisp, + swank-openmcl.lisp, swank-ecl.lisp: Use *gray-stream-symbols* when + importing the needed symbols. + + * swank-gray.lisp (stream-fresh-line): Define a method, so that + Allegro passes our tests. + +2005-09-21 Aleksandar Bakic <a_bakic(a)yahoo.com> + + * swank.lisp (accept-authenticated-connection): Minor fix. Ensure + that the decoded message is a string before calling string= on it. + 2005-09-21 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-setup-command-hooks): Make

1 0

[slime-devel] openmcl: stream-finish-output not exported
by Dave Baum 22 Sep '05

22 Sep '05

A recent change to swank-openmcl.lisp added ccl:stream-finish-output to the import list, but this symbol is not exported in openmcl 0.14.3, so the import causes an error. Dave

2 1

[slime-devel] minor bug fix in accept-authenticated-connection
by Aleksandar Bakic 22 Sep '05

22 Sep '05

Index: swank.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank.lisp,v retrieving revision 1.338 diff -r1.338 swank.lisp 397,399c397,400 < (unless (string= (decode-message new) secret) < (close new) < (error "Incoming connection doesn't know the password."))) --- > (let ((first-val (decode-message new))) > (unless (and (stringp first-val) (string= first-val secret)) > (close new) > (error "Incoming connection doesn't know the password.")))) Alex __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 1

[slime-devel] openmcl: apropos bug fix
by Dave Baum 22 Sep '05

22 Sep '05

The current implementation of describe-symbol-for-emacs assumes that ccl::setf-function-spec-name will always return a symbol. Although this is true for short-form defsetf forms, when the long form has been used, an anonymous function is returned instead of a symbol, which then causes describe-symbol-for-emacs to fail. For example, doing an apropos on "sub" will cause an error because "subseq" has a long form defsetf. Here is a fix: Index: swank-openmcl.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-openmcl.lisp,v retrieving revision 1.101 diff -u -r1.101 swank-openmcl.lisp --- swank-openmcl.lisp 21 Sep 2005 11:43:47 -0000 1.101 +++ swank-openmcl.lisp 22 Sep 2005 02:18:52 -0000 @@ -634,7 +634,8 @@ (maybe-push :setf (let ((setf-function-name (ccl::setf-function-spec-name `(setf ,symbol)))) - (when (fboundp setf-function-name) + (when (or (functionp setf-function-name) ;; long form defsetf + (fboundp setf-function-name)) (doc 'function setf-function-name)))) result)))

1 0

[slime-devel] Problem with SBCL 0.9.4
by Pekka Niiranen 22 Sep '05

22 Sep '05

Hi there, slime (22.9.2005) starts with Clisp ok, but sbcl v0.9.4 gives error: This is SBCL 0.9.4, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/home/pekka/slime/swank-loader.lisp" ; compiling file "/home/pekka/slime/swank-backend.lisp" (written 28 AUG 2005 05:47:11 PM): ; ; compilation unit aborted ; caught 2 fatal ERROR conditions * * The *Messages* windows shows: (emacs) Loading disp-table...done Loading tool-bar...done Loading image...done Loading tooltip...done Loading 00debian-vars...done Loading 20gnus-init (source)...done Loading 49url (source)...done Loading 50autoconf (source)...done Loading 50dictionaries-common (source)... Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...done Loading ispell...done Loading 50dictionaries-common (source)...done Loading 50emacs-goodies-el (source)...done Loading 50w3 (source)...done Loading cl-macs...done Loading cl-seq...done Loading regexp-opt...done Loading easy-mmode...done Loading edmacro...done Loading derived...done Loading byte-opt...done Loading cl-extra...done For information about the GNU Project and its goals, type C-h C-p. Polling "/tmp/slime.5314".. (Abort with `M-x slime-abort-connection'.) [36 times] the number in last line ([36 times]) keeps increasing. I am using Ubuntu 5.04 in AMD64 -pekka-

2 1

[slime-devel] Error in process filter: Wrong type argument: char-or-string-p, :present
by Paolo Amoroso 22 Sep '05

22 Sep '05

I have just updated my CVS copy of SLIME. It works fine with CMUCL Snapshot 2005-09 (19B) and GNU Emacs 21.3.2 under Slackware Linux 10.0, including loading the present.lisp file. But when I try to compile present.lisp from within a SLIME session, I get this error in the Emacs echo area: error in process filter: Wrong type argument: char-or-string-p, :present Compilation of that fine worked fine in earlier versions of SLIME. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

1 1