slime-devel

slime-devel@common-lisp.net

4231 discussions

[Slime-devel] SLY, a fork of SLY
by joaotavora＠gmail.com 08 Sep '14

08 Sep '14

Hi list, For some time now, I've been working on SLY, a fork of SLIME. I believe it is ready to go live now. There's a screencast at https://www.youtube.com/watch?v=xqWkVvubnSI and the project page lives at github http://github.com/capitaomorte/sly.git SLY forked around SLIME 2.4 and is currently on-par with bugfixes in SLIME 2.9. It will continue to track SLIME's bugfixes. A list of changes SLY is available in its NEWS.md file. SLY is still alpha for now. I believe I have done everything right fork-wise, maintaining the licensing notice, crediting the original authors prominently in the README and in any commits cherry-picked from this project. Nevertheless, I invite the current SLIME maintainers to double check-check and notify me so that I can correct any mistakes. Thanks João

9 28

[Slime-devel] Showing two test failures...
by Paul Bowyer 26 Aug '14

26 Aug '14

Hello list, I have a simple bash script that I use to upgrade and test slime that contains the following: ---------------------------------------------------------------------- #! /bin/bash # script name slime-github-setup cd ~/my-slime-sandbox [ -d ./slime ] && rm -rf ./slime #exit #debug exit git clone https://github.com/slime/slime.git cd ~/my-slime-sandbox/slime cd doc make slime.html cd .. #Proper order for these as of 5-22-14 per joao tavora make clean check-fancy make check ---------------------------------------------------------------------- The last time I used it, it ran fine and the test suite completed successfully. Today, however, I find the following two errors: Ran 198 tests, 196 results as expected, 2 unexpected (2014-08-24 18:05:09-0700) 1 expected failures 2 unexpected results: FAILED compile-defun-4 FAILED find-definition\.2-1 make: *** [check] Error 2 Specific error messages: Test compile-defun-4 backtrace: signal(ert-test-failed ("Check failed: error-location-correct")) ert-fail("Check failed: error-location-correct") slime-test-compile-defun("(defun cl-user::foo ()\n (list ` #[nil "\300\301\302\"\207" [slime-test-compile-defun "(defun cl-user byte-code("\306\307!▒q\210\310\216\311 \312\216\313\314\315\316\3 ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc byte-code("\306\307!\211▒\211r\310\311!q\210\312 d\313\223)L\210)\3 ert-run-test([cl-struct-ert-test compile-defun-4 "For input ((defun ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test a ert-run-tests(t #[(event-type &rest event-args) "\30\307\"\203G \ ert-run-tests-batch(t) slime-batch-test(t) eval((slime-batch-test (quote t))) command-line-1(("-L" "." "--eval" "(require 'slime-tests)" "--eval" command-line() normal-top-level() Test compile-defun-4 condition: (ert-test-failed "Check failed: error-location-correct") FAILED 20/198 compile-defun-4 Test find-definition\.2-1 backtrace: signal(ert-test-failed ("Check failed: Definition now at point.")) ert-fail("Check failed: Definition now at point.") slime-test-find-definition\.2("#.(prog1 nil (defvar *foobar* 42))\n\ #[nil "\300\301\302\303#\207" [slime-test-find-definition\.2 "#.(pro byte-code("\306\307!▒q\210\310\216\311 \312\216\313\314\315\316\3 ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc byte-code("\306\307!\211▒\211r\310\311!q\210\312 d\313\223)L\210)\3 ert-run-test([cl-struct-ert-test find-definition\.2-1 "For input (#. ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test a ert-run-tests(t #[(event-type &rest event-args) "\30\307\"\203G \ ert-run-tests-batch(t) slime-batch-test(t) eval((slime-batch-test (quote t))) command-line-1(("-L" "." "--eval" "(require 'slime-tests)" "--eval" command-line() normal-top-level() Test find-definition\.2-1 condition: (ert-test-failed "Check failed: Definition now at point.") FAILED 51/198 find-definition\.2-1 failed 52/198 find-definition\.3-1 SKIPPING: test is currently unstable I just upgraded to SBCL-1.2.2 and decide to upgrade slime also. I'm using GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.8.6). Is there now some reason why my simple script should cause the problem, or are these errors valid? Thanks, Paul Bowyer

4 7

[Slime-devel] SLIME 2.9 released
by Luís Oliveira 04 Aug '14

04 Aug '14

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

1 0

[Slime-devel] Adding to Swank Load-Path
by Samuel Freilich 03 Aug '14

03 Aug '14

Loading a Slime module defined with define-slime-contribs will load its slime-dependencies from anywhere in the Emacs load-path. Swank, however, has its own load-path, so modules with Swank contrib dependencies don't work if they're in a non-default location. For example, if I have a module containing: (require 'slime) (define-slime-contrib my-slime-module "My custom Slime module" (:swank-dependencies my-swank-module)) (provides 'my-slime-module) Then running the following will fail if that module is anywhere other than the default SLIME directory: (require 'my-slime-module) (slime-setup '(my-slime-module)) I've seen two work-arounds, neither of them ideal: 1. Put something in ~/.swank.lisp to modify swank::*load-path*. (That works, but requires more setup and I have to change it if I'm loading from a different directory.) 2. Leave out that dependency from :swank-dependencies and add a hook to 'slime-connected-hook (called after slime-load-contribs) that calls slime-load-file. (That works, but is quite messy.) Is there a supported way for adding directories to the Swank load-path from SLIME? Should define-slime-contrib have a :swank-paths parameter or something? Peace, -Sam

3 2

[Slime-devel] windowed applications on ms windows
by Mick Charles Beaver 06 Jul '14

06 Jul '14

Hello, I have been having trouble with a bug that seems to only occur when running from SLIME, as opposed to the REPL at a CMD prompt. Basically, when I try to run a windowed application, it will hang when opening the window. I do not have any idea why. For example, the following sequence will hang: (ql:quickload "sdl2-examples") (sdl2-examples:basic-test) When trying to debug it further, I found an odd workaround, though. I noticed CCL had some basic win32 samples. In trying to isolate the issue, I ran the following: (defun hack-fix-slime-window () (load "c:/Users/MickBeaver/private/software_packages/ccl/examples/mswin.lisp") (make-simple-ms-window)) That opens a basic win32 window. Afterward, my other windowed applications will start working as expected. So strange! I do not have any issues running from the CMD prompt REPL, though. According to CCL's mswin.lisp, I do not believe I was the first person to encounter this: <snip-start> ;;; At the moment, attempts to create a window when running under SLIME ;;; fail for unknown reasons.<snip-end> Any ideas? System info: GNU Emacs 24.3.1 SLIME 2014-03-27 Microsoft Windows 7 x64 Professional and Microsoft Windows 8 x64 Tried both Clozure Common Lisp 1.9 64-bit and SBCL 1.1.17 64-bit -Mick

2 2

Re: [Slime-devel] [Openmcl-devel] swank test failed ... test-print-arglist & ccl::*print-abbreviate-quote*
by Ben Hyde 24 Jun '14

24 Jun '14

I provided a possible fix to sllme-devel a while ago. But now there is an issue tracker! So I've opened an issue. https://github.com/slime/slime/issues/161 If Gary want's add color commentary there, more power too him.

2 1

[Slime-devel] SBCL Exhausting control stack
by Jason Miller 19 Jun '14

19 Jun '14

SBCL becomes very fragile once the binding stack is exhausted. SLIME seems to do too much in its default error handling to keep the image stable when we encounter this error. Example from the REPL: ;Define a function that will exhaust the stack (defun foo () (declare (optimize (debug 3) (speed 0))) (foo)) (foo) ; The first run of foo can be aborted, but the second time it will hang (foo) A simple workaround would be to wrap any slime invocations with a handler-bind specifically for this case. With the same function #'FOO from earlier, we can do this from the REPL as many times as desired: (handler-bind ((sb-kernel::binding-stack-exhausted-error #'(lambda (c) (invoke-restart 'abort)))) (foo)) Regards, Jason

2 1

[Slime-devel] SLIME compile and load file REPL stays at "CL-USER" with "(in-package :xyz)" in code and not "XYZ"
by Frederik Cheeseman 17 Jun '14

17 Jun '14

When I do C-c C-k (SLIME compile/load file) the REPL stays at "CL-USER". Shouldn't it switch to "MORSE" because of the "(in-package :morse)" code line? I us GNU Emacs 24.3.1, SBCL 1.2.0 and SLIME 2014-04-27.

3 2

[Slime-devel] SLIME 2.7 released
by Luís Oliveira 02 Jun '14

02 Jun '14

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

2 2

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel