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

[slime-devel] Swank documentation
by José Fernandes 01 May '06

01 May '06

Hello. I'm using swank for a school project, so that, in Emacs, I can use Common Lisp to do database related operations. The thing is that Emacs Lisp doesn't have any good package to do database operations (DDL and DML API, socket connection to a database, ACID properties, etc). I've used, as a first try, sql-mode to fire a mysql client process and did all sql operations from there. However it doesn't support some desired properties (rollbacks, etc), the program would be strongly tied to the specific output of mysql client process (I had to parse the output to get the results) and it was a nightmare to make the select queries synchronous (the function would receive a select query string and block while the mysql process outputs the result - and then parse). I chosed CL-SQL as a engine to do DB related operations, and now I need a way to comunicate between Emacs and Common Lisp. I don't know if it is the best way to do it, but I'm using swank as the "bridge" between both. However I don't know, neither can't find documented, the protocol to communicate with swank. Can you help me? Thats all I did until now: I've fired swank in a SBCL console: (require 'swank) (swank::create-swank-server 4006 :spawn #'swank::simple-announce-function t) And then I connect in Emacs: (open-network-stream "swank-process" "swank-buffer" "localhost" 4006) I find "swank-buffer" which reads: 000025(:open-dedicated-output-stream 46912) Then I connect to 46912: (open-network-stream "swank-output" "swank-output-buffer" "localhost" 46912) However as I try to communicate with "swank-process", using (process-send-string), the connection exits abnormally with code 256. In the SBCL console it shows: ;; Swank started at port: 4006. 4006 * ;; Event history start: WRITE: (:open-dedicated-output-stream 46912) ;; Event history end. ;; Connection to Emacs lost. [ ;; condition: junk in string "(+ 2 2" ;; type: SWANK::SLIME-PROTOCOL-ERROR ;; encoding: :ISO-LATIN-1-UNIX style: :SPAWN dedicated: T] debugger invoked on a SIMPLE-ERROR in thread #<THREAD "auto-flush-thread" {B096EE1}>: #<SB-SYS:FD-STREAM for "a constant string" {AF7E3A9}> is closed.

2 2

[slime-devel] Freeze on SLIME development?
by Jonathon McKitrick 28 Apr '06

28 Apr '06

I understand that SLIME has gone 2.0 recently. Is that why the CVS tree has been so quiet? Jonathon McKitrick -- My other computer is your Windows box.

2 1

[slime-devel] sldb buffer not appearing
by Samium Gromoff 27 Apr '06

27 Apr '06

Upon a cvs slime repl-executed load of a certain file i see in the repl buffer a certain error signaled: debugger invoked on a TYPE-ERROR in thread #<THREAD "repl-thread" {B2A4839}>: The value -308655626 is not of type (OR (MOD 536870911) NULL). ... but no sldb buffer appears. SBCL is 0.9.11 regards, Samium Gromoff

1 0

[slime-devel] slime-disconnect
by Takehiko Abe 27 Apr '06

27 Apr '06

Hello Everytime I call slime-disconnect, SLIME-PROTOCOL-ERROR is signaled and swank prints out "Event history". Is this normal? Thanks.

1 0

[slime-devel] encoding problem ?
by Jean-Christophe Helary 26 Apr '06

26 Apr '06

I am just starting to use slime (2.0) and noticed the following problem (which may not be a problem but I can't seem to find a solution): I have a source file that includes Japanese, English and French, it is encoded in UTF-8 and when I load it I get: > invalid byte #xE7 in CHARSET:ASCII conversion > [Condition of type SIMPLE-ERROR] > > Restarts: > 0: [ABORT-REQUEST] Abort handling SLIME request. > 1: [ABORT] ABORT > > Backtrace: > <snip> Is there any way out of this ? If I can't use Unicode to be able to work with multiple languages it really is a pity. Jean-Christophe Helary ps I use CLISP.

4 13

[slime-devel] Trying to connect slime to clisp
by Deb Midya 25 Apr '06

25 Apr '06

Hi! I am a new user to slime 2.0. I want some help to connect slime to clisp 2.38. I have attempted and steps are below. Thanks in advance. 1. Installation of slime 2.0 (Windows XP) I have downloaded slime 2.0 (compressed zipped file) and extracted all the file into /Deb/slime/slime-2.0 2. Installation of clisp 2.38 (Windows XP) I have downloaded clisp-2.38-win32-with-readline-and-gettext which is a compressed (zipped) file. I have unzipped it and put all the files into the directory Deb//clisp/clisp-2.38. 3. Try As per the quick setup instructions of slime in README file, I have created a text file with the following four lines. (add-to-list 'load-path "~/Deb/slime/slime-2.0/") ; your SLIME directory (setq inferior-lisp-program "/Deb/clisp/clisp-2.38") ; your Lisp system (require 'slime) (slime-setup) [Note: I could not follow the line: Add this to your ~/.emacs file and fill in the appropriate filenames:] Where do I get ~/.emacs file? And how can I use the above four lines of commands to connect slime to clisp? I have cut the first line and tried to put it at the command line of clisp, but it does not accept. I have typed manually the first aline at the command line of clisp. It does not work (error: UNDEFINED FUNCTION ADD-TO-LIST). Where as, it accepts the second line. May I request you where am I going wrong? What's the best way of doing it? I am looking forward for your response. Regards Deb --------------------------------- Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.

4 3

[slime-devel] slime2 vs. syntax errors
by Samium Gromoff 24 Apr '06

24 Apr '06

Say i have the following (obviously wrong, but let`s for the sake of argument pretend that i didn`t notice) code: (defstruct foo (bar nil (type (or nil t)))) When i slime-load-file this code i get the following error condition signaled to me via SLDB: Execution of a form compiled with errors. Form: (DEFSTRUCT FOO (BAR NIL (TYPE (OR NIL T)))) Compile-time-error: (during macroexpansion of (DEFSTRUCT FOO ...)) error while parsing arguments to DESTRUCTURING-BIND: odd number of elements in keyword/value list: ((TYPE (OR NIL T))) [Condition of type SB-INT:COMPILED-PROGRAM-ERROR] Restarts: 0: [ABORT] Abort SLIME compilation. 1: [ABORT-REQUEST] Abort handling SLIME request. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "worker" {B6888B1}>) Backtrace: 0: ((SB-C::TOP-LEVEL-FORM (ERROR (QUOTE SB-INT:COMPILED-PROGRAM-ERROR) :MESSAGE "(during macroexpansion of (DEFSTRUCT FOO ...)) error while parsing arguments to DESTRUCTURING-BIND: odd number of elements in keyword/value list: ((TYPE (OR NIL T)))" #1="#<...>" . #1#))) 1: (SB-FASL::LOAD-FASL-GROUP #<SB-SYS:FD-STREAM for "file /home/deepfire/source/sdlsq/tmp.fasl" {B6D3F51}>) 2: (SB-FASL::LOAD-AS-FASL #<SB-SYS:FD-STREAM for "file /home/deepfire/source/sdlsq/tmp.fasl" {B6D3F51}> NIL #<unavailable argument>) 3: (SB-FASL::INTERNAL-LOAD #P"/home/deepfire/source/sdlsq/tmp.fasl" #P"/home/deepfire/source/sdlsq/tmp.fasl" :ERROR NIL NIL :BINARY NIL) 4: (SB-FASL::INTERNAL-LOAD #P"/home/deepfire/source/sdlsq/tmp.fasl" #P"/home/deepfire/source/sdlsq/tmp.fasl" :ERROR NIL NIL NIL :DEFAULT) 5: (LOAD #P"/home/deepfire/source/sdlsq/tmp.fasl") ... So, what is the problem with that? Thing is, you my argue that the error specification is precise enough. However if i want to jump to the source code location which caused this error, after striking 'v' on /any/ entry in the debug stack, i get errors like this: unhandled DEBUG-CONDITION: #<SB-DI::COMPILED-DEBUG-FUN (SB-C::TOP-LEVEL-FORM (ERROR (QUOTE SB-INT:COMPILED-PROGRAM-ERROR) :MESSAGE "(during macroexpansion of (DEFSTRUCT FOO ...)) error while parsing arguments to DESTRUCTURING-BIND: odd number of elements in keyword/value list: ((TYPE (OR NIL T)))" #1="#<...>" . #1#))> has no debug-block information. In fact, observing the debug stack makes it clear that none of its entries bear direct relevance to the source at fault. It points into the guts of the SBCL macroexpander. So this raises the question -- how do i jump to the source location of a syntax error? regards, Samium Gromoff

2 1

[slime-devel] *compiler-notes* stops updating
by Samium Gromoff 23 Apr '06

23 Apr '06

Sometimes the *compiler-notes* buffer stops being updated after slime-load-file invocations. At the point it happens, if i kill that buffer it stops reappearing at all. Slime is version 2.0, SBCL is 0.9.11. regards, Samium Gromoff

1 1

[slime-devel] factual vs. displayed nontrivial warning/note count discrepancy
by Samium Gromoff 23 Apr '06

23 Apr '06

Sometimes i see a significant difference between the SBCL output showing in the slime repl and the reported grand total of warnings/messages at the end of the day -- often slime reports 0 warnings/0 notes despite the presence of the following in the SBCL output: ; caught STYLE-WARNING: ; The variable PERCEPTOR is defined but never used. ; caught STYLE-WARNING: ; These functions are undefined: ; ENTITY-MOVE-COLLIDES? ENTITY-MOVECUM ; caught STYLE-WARNING: ; undefined function: ENTITY-MOVECUM etc etc This is noticed with slime 2.0/sbcl 0.9.11 regards, Samium Gromoff

1 0

[slime-devel] pathname on a socket stream
by Marco Baringer 23 Apr '06

23 Apr '06

this came up when trying to use slime's inspector to inspect a socket connected to a remote server. the following snippet signals an error: CL-USER> (let* ((socket (make-instance 'sb-bsd-sockets:inet-socket :type :stream :protocol :tcp))) (sb-bsd-sockets:socket-connect socket #(127 0 0 1) 8080) (sb-bsd-sockets:socket-make-stream socket)) #<SB-SYS:FD-STREAM for "a constant string" {40D28759}> CL-USER> (pathname *) Error: The value NIL is not of type PATHNAME. [Condition of type TYPE-ERROR] however, substitiuting the call to pathname for its definiton return NIL: CL-USER> (let* ((socket (make-instance 'sb-bsd-sockets:inet-socket :type :stream :protocol :tcp))) (sb-bsd-sockets:socket-connect socket #(127 0 0 1) 8080) (sb-impl::with-pathname (pathname (sb-bsd-sockets:socket-make-stream socket)) pathname)) NIL CL-USER> i'm not really sure what the correct answer is, according to the hyperspec pathname must return a pathname object and NIL is definetly not a pathname object. at the same time a file stream is a pathname designator and pathname is defined to accept pathname designator (the hyperspec doesn't mention any exceptional situations). is there some (non neccessarily portable) means to determine if a stream is a valid value for passing to pathname? -- -Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

1 1