slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] macro-indentation should ignore &optional
by darkness 10 Feb '06

10 Feb '06

Greetings. I've got a macro like: (defmacro tbf (&optional bar &body baz) ...) With SLIME from CVS, this gets indented as: (tbf (:arg value) (form1) (form2)) Whereas I think the correct indentation should be: (tbf (:arg value) (form1) (form2)) The problem (as I see it) is that swank:macro-indent counts &optional as an argument, rather than as a lambda list keyword. Below is a simple patch against SLIME CVS. =================================================================== RCS file: /project/slime/cvsroot/slime/swank.lisp,v retrieving revision 1.360 diff -u -r1.360 swank.lisp --- swank.lisp 6 Feb 2006 18:42:09 -0000 1.360 +++ swank.lisp 9 Feb 2006 17:16:26 -0000 @@ -4369,7 +4369,7 @@ (defun macro-indentation (arglist) (if (well-formed-list-p arglist) - (position '&body (clean-arglist arglist)) + (position '&body (remove '&optional (clean-arglist arglist))) nil)) (defun well-formed-list-p (list)

2 1

[slime-devel] Emacs freezing bug fix
by Timofei Shatrov 10 Feb '06

10 Feb '06

I found a fix for a bug that plagued me for a long time. Whenever I was connected to Internet, Slime was consistently hanging Emacs cold. The bug apparently stems from make-network-process function of Emacs which demonstrates the same behavior. Anyway, there is a fix: replace all occurences of "127.0.0.1" in slime.el with "localhost" - surprisingly this solves the problem. -- Best regards, Timofei Shatrov mailto:grue@mail.ru

2 1

RE: [slime-devel] Re: Slime inserting an extra parenthesis
by Bradford W Miller 07 Feb '06

07 Feb '06

I smell a project: http://www.rci.rutgers.edu/~cfs/472_html/Planning/PlanRecog.html Unfortunately, it's close enough to my day job I'd have IP problems doing the work. But I'd be happy to kibitz. -----Original Message----- From: slime-devel-bounces(a)common-lisp.net [mailto:slime-devel-bounces@common-lisp.net] On Behalf Of edi(a)agharta.de Sent: Tuesday, February 07, 2006 6:49 AM To: jan(a)rychter.com Cc: slime-devel(a)common-lisp.net Subject: Re: [slime-devel] Re: Slime inserting an extra parenthesis On Tue, 07 Feb 2006 10:27:40 +0100, Jan Rychter <jan(a)rychter.com> wrote: > Right, well -- but shouldn't completion be smart enough to know if > the parentheses should be closed or not? At the moment I can't really imagine how SLIME should be able to always do The Right Thing[TM] unless it can read your mind. But I think patches are always welcome. _______________________________________________ slime-devel site list slime-devel(a)common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel

1 0

[edi@agharta.de: Re: [slime-devel] Re: Slime inserting an extra parenthesis]
by Jeff Cunningham 07 Feb '06

07 Feb '06

> I don't get the described behavior in gnu-emacs. Must be an xemacs > thing. >... > Actually, I just noticed that in this case M-q does manage to do the > 'right thing' with the parenthesis. Try that. That was probably meant for the list. I don't have a problem with SLIME's handling of parentheses, the OP has. Cheers, Edi. Sorry, Edi, I thought I was mailing this to the list. -Jeff

1 0

[slime-devel] Slime inserting an extra parenthesis
by Jan Rychter 07 Feb '06

07 Feb '06

I often use insert-parentheses in XEmacs, and it seems to interact badly with SLIME. An example: I begin with: CL-USER> () ^point I then type asdf-u<TAB>:u<TAB> and end up with this: CL-USER> (asdf-upgrade:upgrade)) ^point Notice the extra parenthesis that SLIME inserted. My guess is that SLIME shouldn't insert this parenthesis. I can understand where this came from (no extra args, so the user surely wants to close the parenthesis), but for someone mostly working with balanced parentheses this isn't too useful. --J.

2 3

[slime-devel] patch: make slime-echo-arglist show initargs/initforms for make-instance
by Luís Oliveira 06 Feb '06

06 Feb '06

Hello, The attached patch makes slime-echo-arglist detect (make-instance 'quoted-symbol ...) forms and uses the quoted symbol to find the class and present the initargs and initforms in the mini-buffer. For example: CL-USER> (defclass foo () ((a :initarg :initarg-a :initform nil) (b :initarg :initarg-b) c)) #<STANDARD-CLASS FOO> CL-USER> (make-instance<space> ;; minibuffer displays: (make-instance class &rest initargs) CL-USER> (make-instance 'foo<space> ;; minibuffer displays: (make-instance 'foo &key (initarg-a nil) initarg-b) The code is a bit ugly, specially on the elisp side. My elisp-fu being very weak doesn't help. Suggestions on how to improve that are most welcome! BTW, the ChangeLog's encoding seems to be latin-1, wouldn't utf-8 be better? -- Luís Oliveira luismbo (@) gmail (.) com Equipa Portuguesa do Translation Project http://www.iro.umontreal.ca/translation/registry.cgi?team=pt

2 3

[slime-devel] Followup on dangerous bug
by Bradford W. Miller 06 Feb '06

06 Feb '06

Last week I reported on a problem where a buffer in the slime-typeout window would be overwritten if the *SLIME-Typeout* buffer is killed by the user. A suggested fix follows: The code calls the function slime-typeout-active-p in order to assure the window is open. However, this call does NOT insure that the correct buffer is exposed in that window. The saved window is in the variable "slime-typeout-window", but this will reflect any exposed buffer in that window, not "*SLIME-Typeout*". I have modified the slime-typeout-active-p function as follows, to make sure that the window has the correct buffer in the foreground before the caller does the write. (There is still the potential for a collision if the buffer is switched between calling this function and writing to it, however, I'm unfamiliar with mechanisms for locking frames in emacs to prevent that). Instead, perhaps for full safety, the call (window-buffer slime-typeout-window) in slime-typeout- message should be (get-buffer-create "*SLIME-Typeout*") instead. That way the write always occurs to the correct buffer, and not the one that happens to be exposed. At least on my local copy, these functions works normally, and killing *SLIME-Typeout* causes it to be restored before, e.g., showing the arglist for the function at prompt while in the slime REPL. These patches fix two problems: 1) that the use of the typeout window may go to the wrong buffer if the wrong buffer happens to be exposed and 2) that the *SLIME-Typeout* buffer is not exposed in the window created for that express purpose. Allow me to suggest these patchs for inclusion in the CVS. (defun slime-typeout-active-p () ;; modified 2/6/06 BWM (cond ((and slime-typeout-window (window-live-p slime-typeout-window)) (save-selected-window (select-window slime-typeout-window) (switch-to-buffer "*SLIME-Typeout*")) t) ; return true -it's active and ready (t nil))) (defun slime-typeout-message (format-string &rest format-args) (assert (slime-typeout-active-p)) (with-current-buffer (get-buffer-create "*SLIME-Typeout*") ;; modified 2/6/06 BWM (erase-buffer) (insert (apply #'format format-string format-args))))

1 0

[slime-devel] Bug fix for inspecting logical-pathnames
by Lynn Quam 05 Feb '06

05 Feb '06

There is a missing comma for backquote substitution in the following method that causes an error when inpecting logical-pathnames using SLIME. Error in function SWANK::INSPECTOR-CONTENT-FOR-EMACS: destructure-case failed: (PATHNAME-HOST PATHNAME) [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] ABORT 1: [ABORT-REQUEST] Abort handling SLIME request. 2: [ABORT] Return to Top-Level. Backtrace: 0: (SWANK::INSPECTOR-CONTENT-FOR-EMACS ("Namestring" ": " (:VALUE "FREEDIUS:LISP;MATH;MATRICES.LISP") (:NEWLINE) "Physical pathname: " ...)) 1: (SWANK::INSPECT-OBJECT #P"FREEDIUS:LISP;MATH;MATRICES.LISP" #<SWANK-BACKEND::CMUCL-INSPECTOR {5BA62CBD}>) ... The literal form (pathname-host pathname) gets passed to SWANK::INSPECTOR-CONTENT-FOR-EMACS instead of its value. I have added the comma in the line indicated by ; <<< COMMA NEEDED HERE (defmethod inspect-for-emacs ((pathname logical-pathname) inspector) (declare (ignore inspector)) (values "A logical pathname." (append (label-value-line* ("Namestring" (namestring pathname)) ("Physical pathname: " (translate-logical-pathname pathname))) `("Host: " ,(pathname-host pathname) ; <<< COMMA NEEDED HERE " (" (:value ,(logical-pathname-translations (pathname-host pathname))) "other translations)" (:newline)) (label-value-line* ("Directory" (pathname-directory pathname)) ("Name" (pathname-name pathname)) ("Type" (pathname-type pathname)) ("Version" (pathname-version pathname)) ("Truename" (if (not (wild-pathname-p pathname)) (probe-file pathname)))))))

1 0

[slime-devel] #<STANDARD-GENERIC-FUNCTION SWANK-BACKEND:CREATE-SOCKET (0)>
by Prashant Acharekar 04 Feb '06

04 Feb '06

HI, I am new to LISP. I am using MAC OS X version 10.4. I am using aquamacs Emacs. I have downloaded slime from http://common-lisp.net/cgi-bin/viewcvs.cgi/?root=slime And i am using SBCL. When i tried to run the slime using M-x. i encounterd following error. (load "/Users/hrush/slime/swank-loader.lisp" :verbose t) (swank:start-server "/tmp/slime.394" :external-format :iso-latin-1-unix) This is SBCL 0.9.7, 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"/Users/hrush/slime/swank-loader.lisp" ; compiling file "/Users/hrush/slime/swank-backend.lisp" (written 31 JAN 2006 01:26:55 AM): ; /Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-backend.fasl written ; compilation finished in 0:00:04 ;; loading #P"/Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-backend.fasl" WARNING: SWANK-BACKEND also exports the following symbols: (SWANK-BACKEND:MAKE-WEAK-VALUE-HASH-TABLE SWANK-BACKEND:FRAME-CATCH-TAGS SWANK-BACKEND:ADD-SIGIO-HANDLER SWANK-BACKEND:FORMAT-SLDB-CONDITION SWANK-BACKEND:PROFILE-PACKAGE SWANK-BACKEND:RESTART-FRAME SWANK-BACKEND:DEFAULT-DIRECTORY SWANK-BACKEND:FRAME-SOURCE-LOCATION-FOR-EMACS SWANK-BACKEND:MAKE-WEAK-KEY-HASH-TABLE SWANK-BACKEND:COMPUTE-BACKTRACE SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK SWANK-BACKEND:INITIALIZE-MULTIPROCESSING SWANK-BACKEND:LIST-CALLEES SWANK-BACKEND:REMOVE-FD-HANDLERS SWANK-BACKEND:RECEIVE SWANK-BACKEND:COMPILER-MACROEXPAND-1 SWANK-BACKEND:REMOVE-SIGIO-HANDLERS SWANK-BACKEND:ACCEPT-CONNECTION SWANK-BACKEND:THREAD-NAME SWANK-BACKEND:UNPROFILE SWANK-BACKEND:TOGGLE-TRACE SWANK-BACKEND:THREAD-ALIVE-P SWANK-BACKEND:CLOSE-SOCKET SWANK-BACKEND:DESCRIBE-SYMBOL-FOR-EMACS SWANK-BACKEND:SPAWN SWANK-BACKEND:MAKE-DEFAULT-INSPECTOR SWANK-BACKEND:SLDB-BREAK-AT-START SWANK-BACKEND:FIND-DEFINITIONS SWANK-BACKEND:WHO-SPECIALIZES SWANK-BACKEND:THREAD-STATUS SWANK-BACKEND:CONDITION-EXTRAS SWANK-BACKEND:FUNCTION-NAME SWANK-BACKEND:OPERATE-ON-SYSTEM SWANK-BACKEND:UNPROFILE-ALL SWANK-BACKEND:EVAL-IN-FRAME SWANK-BACKEND:FIND-THREAD SWANK-BACKEND:SLDB-BREAK-ON-RETURN SWANK-BACKEND:WHO-REFERENCES SWANK-BACKEND:LOCAL-PORT SWANK-BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT SWANK-BACKEND:PROFILED-FUNCTIONS SWANK-BACKEND:SEND SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS SWANK-BACKEND:EMACS-CONNECTED SWANK-BACKEND:WHO-BINDS SWANK-BACKEND:MAKE-LOCK SWANK-BACKEND:CREATE-SOCKET SWANK-BACKEND:BUFFER-FIRST-CHANGE SWANK-BACKEND:SET-DEFAULT-DIRECTORY SWANK-BACKEND:PROFILE-RESET SWANK-BACKEND:FRAME-VAR-VALUE SWANK-BACKEND:MACROEXPAND-ALL SWANK-BACKEND:CURRENT-THREAD SWANK-BACKEND:STARTUP-IDLE-AND-TOP-LEVEL-LOOPS SWANK-BACKEND:ACTIVATE-STEPPING SWANK-BACKEND:DISASSEMBLE-FRAME SWANK-BACKEND:SWANK-COMPILE-FILE SWANK-BACKEND:PROFILE-REPORT SWANK-BACKEND:CALL-WITH-LOCK-HELD SWANK-BACKEND:FRAME-LOCALS SWANK-BACKEND:ALL-THREADS SWANK-BACKEND:DESCRIBE-DEFINITION SWANK-BACKEND:WHO-SETS SWANK-BACKEND:CALL-WITH-COMPILATION-HOOKS SWANK-BACKEND:MAKE-FN-STREAMS SWANK-BACKEND:LISP-IMPLEMENTATION-TYPE-NAME SWANK-BACKEND:ARGLIST SWANK-BACKEND:RETURN-FROM-FRAME SWANK-BACKEND:LIST-CALLERS SWANK-BACKEND:PREFERRED-COMMUNICATION-STYLE SWANK-BACKEND:ADD-FD-HANDLER SWANK-BACKEND:KILL-THREAD SWANK-BACKEND:CALL-WITHOUT-INTERRUPTS SWANK-BACKEND:COMPILER-MACROEXPAND SWANK-BACKEND:CONDITION-REFERENCES SWANK-BACKEND:THREAD-ID SWANK-BACKEND:PRINT-FRAME SWANK-BACKEND:GETPID SWANK-BACKEND:DESCRIBE-PRIMITIVE-TYPE SWANK-BACKEND:PROFILE SWANK-BACKEND:SWANK-COMPILE-STRING SWANK-BACKEND:MAKE-STREAM-INTERACTIVE SWANK-BACKEND:DEFAULT-READTABLE-ALIST SWANK-BACKEND:WHO-CALLS SWANK-BACKEND:INTERRUPT-THREAD SWANK-BACKEND:INSTALL-DEBUGGER-GLOBALLY SWANK-BACKEND:WHO-MACROEXPANDS SWANK-BACKEND:CALLS-WHO) See also: The ANSI Standard, Macro DEFPACKAGE ; compiling file "/Users/hrush/slime/nregex.lisp" (written 19 SEP 2005 01:50:48 PM): ; /Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/nregex.fasl written ; compilation finished in 0:00:01 ;; loading #P"/Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/nregex.fasl" ; compiling file "/Users/hrush/slime/swank-sbcl.lisp" (written 21 JAN 2006 03:01:20 AM): compilation aborted because of fatal error: READ failure in COMPILE-FILE: READER-ERROR at 1066 (line 42, column 41) on #<SB-SYS:FD-STREAM for "file /Users/hrush/slime/swank-sbcl.lisp" {1036A8B1}>: package "SB-BSD-SOCKETS" not found ; /Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-sbcl.fasl written ; compilation finished in 0:00:01 ;; loading #P"/Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-sbcl.fasl" STYLE-WARNING: redefining PREFERRED-COMMUNICATION-STYLE NIL in DEFMETHOD ; compiling file "/Users/hrush/slime/swank-source-path-parser.lisp" (written 07 NOV 2005 01:54:32 PM): ; /Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-source-path-parser.fasl written ; compilation finished in 0:00:00 ;; loading #P"/Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-source-path-parser.fasl" ; compiling file "/Users/hrush/slime/swank-source-file-cache.lisp" (written 30 AUG 2005 01:32:58 AM): ; /Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-source-file-cache.fasl written ; compilation finished in 0:00:00 ;; loading #P"/Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-source-file-cache.fasl" STYLE-WARNING: redefining BUFFER-FIRST-CHANGE (T) in DEFMETHOD ; compiling file "/Users/hrush/slime/swank-gray.lisp" (written 23 SEP 2005 01:45:11 AM): ; /Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-gray.fasl written ; compilation finished in 0:00:02 ;; loading #P"/Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank-gray.fasl" STYLE-WARNING: implicitly creating new generic function STREAM-READ-CHAR-WILL-HANG-P ; compiling file "/Users/hrush/slime/swank.lisp" (written 31 JAN 2006 01:26:55 AM): ; /Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank.fasl written ; compilation finished in 0:00:10 ;; loading #P"/Users/hrush/.slime/fasl/sbcl-0.9.7-darwin-ppc/swank.fasl" WARNING: SWANK also exports the following symbols: (SWANK:INIT-INSPECTOR SWANK:INSPECT-IN-FRAME SWANK:INSPECT-NTH-PART SWANK:GET-REPL-RESULT SWANK:XREF SWANK:TAKE-INPUT SWANK:START-SWANK-SERVER-IN-THREAD SWANK:INSPECT-FRAME-VAR SWANK:SWANK-MACROEXPAND SWANK:LOAD-FILE-SET-PACKAGE SWANK:APROPOS-LIST-FOR-EMACS SWANK:DESCRIBE-FUNCTION SWANK:COMPLETE-FORM SWANK:SLDB-BREAK-WITH-DEFAULT-DEBUGGER SWANK:COMMIT-EDITED-VALUE SWANK:INSPECTOR-POP SWANK:TOGGLE-PROFILE-FDEFINITION SWANK:LIST-ALL-PACKAGE-NAMES SWANK:SLDB-DISASSEMBLE SWANK:FUZZY-COMPLETION-SELECTED SWANK:INSPECTOR-REINSPECT SWANK:LISTENER-EVAL SWANK:LIST-THREADS SWANK:QUIT-INSPECTOR SWANK:REPL-EVAL-HOOK-PASS SWANK:DOCUMENTATION-SYMBOL SWANK:DESCRIBE-INSPECTEE SWANK:DISASSEMBLE-SYMBOL SWANK:BACKTRACE SWANK:INVOKE-NTH-RESTART-FOR-EMACS SWANK:REPL-SUPPRESS-ADVANCE-HISTORY SWANK:RE-EVALUATE-DEFVAR SWANK:FIND-DEFINITIONS-FOR-EMACS SWANK:PPRINT-EVAL-STRING-IN-FRAME SWANK:DESCRIBE-SYMBOL SWANK:FRAME-LOCALS-FOR-EMACS SWANK:DEBUGGER-INFO-FOR-EMACS SWANK:REPL-SUPPRESS-OUTPUT SWANK:ARGLIST-FOR-INSERTION SWANK:CLEAR-REPL-RESULTS SWANK:SLDB-ABORT SWANK:SLDB-RETURN-FROM-FRAME SWANK:FRAME-CATCH-TAGS-FOR-EMACS SWANK:SWANK-TOGGLE-TRACE SWANK:UNTRACE-ALL SWANK:SIMPLE-COMPLETIONS SWANK:KILL-NTH-THREAD SWANK:EVAL-STRING-IN-FRAME SWANK:OPERATE-ON-SYSTEM-FOR-EMACS SWANK:THROW-TO-TOPLEVEL SWANK:COMPILER-NOTES-FOR-EMACS SWANK:UPDATE-INDENTATION-INFORMATION SWANK:VARIABLE-DESC-FOR-ECHO-AREA SWANK:INTERACTIVE-EVAL SWANK:PPRINT-INSPECTOR-PART SWANK:COMPILE-FILE-FOR-EMACS SWANK:SWANK-COMPILER-MACROEXPAND-1 SWANK:SET-PACKAGE SWANK:INVOKE-NTH-RESTART SWANK:INSPECTOR-NEXT SWANK:DEBUG-NTH-THREAD SWANK:SWANK-MACROEXPAND-1 SWANK:SLDB-CONTINUE SWANK:DESCRIBE-DEFINITION-FOR-EMACS SWANK:COMPILE-FILE-IF-NEEDED SWANK:INSPECTOR-CALL-NTH-ACTION SWANK:SIMPLE-BREAK SWANK:STATE-STACK SWANK:SWANK-MACROEXPAND-ALL SWANK:PPRINT-EVAL SWANK:LOAD-FILE SWANK:ARGLIST-FOR-ECHO-AREA SWANK:CONNECTION-INFO SWANK:EVAL-AND-GRAB-OUTPUT SWANK:IO-SPEED-TEST SWANK:UNDEFINE-FUNCTION SWANK:COMPILE-STRING-FOR-EMACS SWANK:MOP SWANK:INTERACTIVE-EVAL-REGION SWANK:SWANK-COMPILER-MACROEXPAND SWANK:COMPLETIONS SWANK:LIST-ALL-SYSTEMS-IN-CENTRAL-REGISTRY SWANK:VALUE-FOR-EDITING SWANK:INSPECT-CURRENT-CONDITION SWANK:INSPECTOR-NTH-PART SWANK:FUZZY-COMPLETIONS SWANK:QUIT-THREAD-BROWSER) See also: The ANSI Standard, Macro DEFPACKAGE STYLE-WARNING: redefining PREFIXED-VAR in DEFUN STYLE-WARNING: implicitly creating new generic function INSPECT-BIGGER-PIECE-ACTIONS STYLE-WARNING: implicitly creating new generic function INSPECT-WHOLE-THING-ACTION STYLE-WARNING: implicitly creating new generic function INSPECT-SHOW-MORE-ACTION STYLE-WARNING: implicitly creating new generic function MENU-CHOICES-FOR-PRESENTATION ; ; compilation unit finished ; caught 1 fatal ERROR condition WARNING: These Swank interfaces are unimplemented: (ACCEPT-CONNECTION ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER ALL-THREADS CALL-WITH-COMPILATION-HOOKS CALL-WITH-DEBUGGING-ENVIRONMENT CALLS-WHO CLOSE-SOCKET COMPUTE-BACKTRACE CREATE-SOCKET DESCRIBE-DEFINITION DESCRIBE-SYMBOL-FOR-EMACS DISASSEMBLE-FRAME EVAL-IN-FRAME FIND-DEFINITIONS FIND-THREAD FRAME-CATCH-TAGS FRAME-LOCALS FRAME-SOURCE-LOCATION-FOR-EMACS FRAME-VAR-VALUE GETPID INSPECT-FOR-EMACS INTERRUPT-THREAD LIST-CALLEES LIST-CALLERS LOCAL-PORT MACROEXPAND-ALL MAKE-DEFAULT-INSPECTOR PRINT-FRAME PROFILE PROFILE-PACKAGE PROFILE-REPORT PROFILE-RESET PROFILED-FUNCTIONS QUIT-LISP RECEIVE REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS RESTART-FRAME RETURN-FROM-FRAME SEND SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN SPAWN SWANK-COMPILE-FILE SWANK-COMPILE-STRING THREAD-ID TOGGLE-TRACE UNPROFILE WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) T * debugger invoked on a SIMPLE-ERROR: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION SWANK-BACKEND:CREATE-SOCKET (0)> when called with arguments ("127.0.0.1" 0). Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION SWANK-BACKEND:CREATE-SOCKET (0)> ("127.0.0.1" 0)) 0] 0 While i was searching on the net i came across page http://common-lisp.net/pipermail/slime-devel/2005-October/004179.html I tried allthe things still things are not working. can you please help me out. ,Percy.

2 1

[slime-devel] SBCL Win32
by Jeremy Shute 04 Feb '06

04 Feb '06

I have recently discovered that Windows now has SBCL releases. I just about fell out of my chair -- the day is nigh! When I try to fire up CVS head SLIME, I get this: ; loading #P"c:\\lisp\\slime\\swank-loader.lisp" debugger invoked on a UNDEFINED-FUNCTION: The function SB-UNIX:UNIX-GETUID is undefined. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (SB-KERNEL::UNDEFINED-FUN-ERROR-HANDLER #<unavailable argument> #.(SB-SYS:INT-SAP #X0022F3C4) #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X0022F0CC :TYPE (* (SB-ALIEN:STRUCT SB-VM::OS-CONTEXT-T-STRUCT))> (14)) 0] Being somewhat enamored, I'd like to help... * (apropos 'uid) UID :SB-FLUID (bound) SB-UNIX:ST-UID SB-UNIX:UNIX-GETUID SB-UNIX:SETUIDEXEC SB-UNIX:UID-HOMEDIR SB-UNIX:UID-USERNAME SB-UNIX:UNIX-UID SB-UNIX:S-ISUID SB-UNIX:UID-T * (describe 'sb-unix:unix-uid) SB-UNIX:UNIX-UID is an external symbol in #<PACKAGE "SB-UNIX">. It names a type specifier. The type is there, but not the function to generate instances of it. Who's working on this, where's the code, and what can I do to help? Jeremy

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