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

Re: [Slime-devel] I think I need a little help
by Paul Bowyer 30 May '14

30 May '14

Hello João, I discovered something today about the debug window problem I'm having with slime. I have a little-used installation of Linux Mint 16 on a different partition of my hard drive and I spent some time today going through the steps to load Emacs 24.3.1, along with sbcl-1.1.18, and all of the other folders and files that it took to make it as similar as possible to my installation of Linux Mint 14. I had a little problem initially until I remembered to install quicklisp and then I downloaded a fresh copy of slime using my install script and started emacs-24, did M-x slime, and there was no unwanted debug window in emacs. I quit and restarted slime several times and each time it came up without the unwanted debug window. It seems the slime debug window problem is specific to my installation of Linux Mint 14. I can only guess that I have done something to cause the problem, but I have no idea what it might have been. I'm usually very careful about installing anything that might cause a problem, but maybe I did something stupid... Anyway, to make a long story short, I'm going to migrate my work system files over to the Linux Mint 16 installation and then clean up my work partition to use for the next new release of Linux Mint (I kind of like it). If you are searching for the elusive debug window problem, I suspect you'll never find it on a different system so I suggest you cease and call it wasted effort because of me. Thanks again for all of your help, Paul Bowyer

2 1

[Slime-devel] Freeze for SLIME 2.7
by Luís Oliveira 29 May '14

29 May '14

Hello everyone, May was relatively slow but, as increasingly usual, please focus on testing and fixing regressions since the last release for the next few days. I plan to release SLIME 2.7 next Sunday. Cheers, -- Luís Oliveira http://kerno.org/~luis/

1 0

[Slime-devel] I think I need a little help
by Paul Bowyer 23 May '14

23 May '14

Hello everyone, I've recently tried to use Emacs 24.1.1 which is available from the repository of Linux Mint and I cannot get slime to run properly with it. I'm using slime from github which I get with "git clone https://github.com/slime/slime.git" and I'm using SBCL-1.1.18. I tried using a very basic ".emacs" file by following the directions in the slime manual ------------------------------------------------------------------------------- ;;Latest slime installation (add-to-list 'load-path "~/my-slime-sandbox/slime/") (require 'slime-autoloads) (setq inferior-lisp-program "/usr/local/bin/sbcl" ) (setq slime-contribs '(slime-fancy)) ;;This fails to load properly ------------------------------------------------------------------------------- The message I get in the emacs message when I try ALT-x slime window is: define-slime-contrib: Symbol's value as variable is void: --cl---cl-var--11849-- I also ran the slime test suite using the same emacs with the following sequence of commands that I have in a bash script. ------------------------------------------- cd ~/my-slime-sandbox/slime make clean make compile #Run the test suite make clean check make check-fancy ------------------------------------------- The output of the test is: <snip> Test readme-recipe condition: (ert-test-failed "Unexpected error running takeoff forms\n(void-variable --cl---cl-var--99749--)") FAILED 61/186 readme-recipe <snip> Test traditional-recipe condition: (ert-test-failed "Unexpected error running preflight forms\n(void-variable --cl---cl-var--99749--)") FAILED 183/186 traditional-recipe <snip> Ran 186 tests, 184 results as expected, 2 unexpected (2014-05-20 17:41:21-0700) 1 expected failures 2 unexpected results: FAILED readme-recipe FAILED traditional-recipe make: *** [check] Error 2 make -C contrib EMACS="emacs" LISP="sbcl" check-fancy make[1]: Entering directory `/home/pfb/my-slime-sandbox/slime/contrib' emacs -Q -L . -L .. --batch -f batch-byte-compile slime-sprof.el In toplevel form: slime-sprof.el:5:1:Error: Symbol's value as variable is void: --cl---cl-var--99749-- make[1]: *** [slime-sprof.elc] Error 1 make[1]: Leaving directory `/home/pfb/my-slime-sandbox/slime/contrib' make: *** [check-fancy] Error 2 That's as much as I can tell you about my problem. Paul Bowyer

3 7

Re: [Slime-devel] [Openmcl-devel] swank test failed ... test-print-arglist & ccl::*print-abbreviate-quote*
by Mark H. David 22 May '14

22 May '14

I’m trying to bring this up again, and also now sending it to slime-devel. I would like this warning to be gone. Can anyone fix it? On Mar 9, 2013, at 1:57 PM, Ben Hyde <bhyde(a)pobox.com> wrote: > Each time swank loaded it runs (swank::test-print-arglist) which complains: > > ; Warning: Test failed: (&key #'#'+) => "(&key (function (function +)))" > ; Expected: "(&key (function #'+))" > ; While executing: (:internal test test-print-arglist), in process worker(8). > > That's due to this… > > swank> (decoded-arglist-to-string (decode-arglist '(&key (function #'+)))) > "(&key (function (function +)))" > > Decoded-arglist-to-string is in swank-arglists.lisp. It is using with-standard-io-syntax. That binds ccl::*print-abbreviate-quote* to nil. If I force it to T in decoded-arglist-to-string the test "passes." > > It is certainly beyond the scope of my expertise etc. to determine where if anyplace the bug lies. Though this seems odd to me: > > $ ccl64 --no-init > Welcome to Clozure Common Lisp Version 1.9-r15759 (DarwinX8664)! > ? (values ccl::*print-abbreviate-quote* (with-standard-io-syntax ccl::*print-abbreviate-quote*)) > T > NIL > ? > > wdyt? > > - ben > _______________________________________________ > Openmcl-devel mailing list > Openmcl-devel(a)clozure.com > http://clozure.com/mailman/listinfo/openmcl-devel

1 0

Re: [Slime-devel] [slime-devel] abcl as an inferior lisp program
by bonasso 16 May '14

16 May '14

1 0

[Slime-devel] Is it possible to get double-float from lisp?
by Leo Liu 10 May '14

10 May '14

Due to different syntaxes for floats: (slime-eval `(anything-that-poduces-double-floats)) => a variable I wonder if this is curable? Thanks. Leo

2 1

[Slime-devel] ACL bits
by mega＠retes.hu 08 May '14

08 May '14

I implemented FUNCTION-NAME and FIND-SOURCE-LOCATION for AllegroCL and requested a pull on github: https://github.com/slime/slime/pull/142 Is this enough or shall I write to this list as well? :-) cheers, Gabor

2 3

[Slime-devel] SLIME 2.6 released
by Luís Oliveira 04 May '14

04 May '14

Hello all, SLIME 2.6 is released! https://github.com/slime/slime/releases/tag/v2.6 Cheers, -- Luís Oliveira http://kerno.org/~luis/

1 0

[Slime-devel] A problem?
by Paul Bowyer 02 May '14

02 May '14

Hello everyone, This morning after I started my computer, I tried slime again and to my surprise it came up without a whimper. What ever was the problem yesterday that was causing the sldb window cleared itself after this morning's boot. I hope you haven't spent a lot of time searching for a non-existent problem and I apologize for the faulty report. Paul Bowyer

1 0

[Slime-devel] A problem?
by Paul Bowyer 02 May '14

02 May '14

Hello everyone, Today I upgraded slime using "git clone https://github.com/slime/slime.git" after I upgraded sbcl from version 1.1.17 to version 1.1.18. Slime completed the test suite without errors with emacs-23.4.1. When I do ALT-x slime in emacs, a *sldb sbcl/1* window opens with the following: Interrupt thread failed: thread #<THREAD "Swank 40905" FINISHED values: NIL {100343B723}> has exited. [Condition of type SB-THREAD:INTERRUPT-THREAD-ERROR] Restarts: 0: [ABORT] Abort thread (#<THREAD "Swank Sentinel" RUNNING {100343B343}>) Backtrace: 0: (SB-THREAD:INTERRUPT-THREAD #<SB-THREAD:THREAD "Swank 40905" FINISHED values: NIL {100343B723}> #<FUNCTION (LAMBDA NIL :IN SB-THREAD:TERMINATE-THREAD) {1001C9062B}>) 1: (SWANK::SENTINEL-SERVE (:STOP-SERVER :SOCKET #<SB-BSD-SOCKETS:INET-SOCKET fd: -1 {100336FAB3}>)) 2: (SWANK::SENTINEL) 3: ((FLET #:WITHOUT-INTERRUPTS-BODY-1226 :IN SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE)) 4: ((FLET SB-THREAD::WITH-MUTEX-THUNK :IN SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE)) 5: ((FLET #:WITHOUT-INTERRUPTS-BODY-660 :IN SB-THREAD::CALL-WITH-MUTEX)) 6: (SB-THREAD::CALL-WITH-MUTEX #<CLOSURE (FLET SB-THREAD::WITH-MUTEX-THUNK :IN SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE) {7FFFF675EC2B}> #<SB-THREAD:MUTEX "thread result lock" owner: #<SB-THREAD:THR.. 7: (SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE #<SB-THREAD:THREAD "Swank Sentinel" RUNNING {100343B343}> #S(SB-THREAD:SEMAPHORE :NAME "Thread setup semaphore" :%COUNT 0 :WAITCOUNT 0 :MUTEX #<SB-THREAD.. 8: ("foreign function: call_into_lisp") 9: ("foreign function: new_thread_trampoline") If I choose abort, it closes the sldb window and leaves me with a running repl, but I'm uncertain everything is OK. Don't really know what to do next. Thanks for any pointers, Paul Bowyer

1 0