slime-devel

slime-devel@common-lisp.net

4231 discussions

slime on github
by Paul Bowyer 08 Apr '15

08 Apr '15

Hello Helmut, I've recently become aware the slime is now on github, so I downloaded and installed a copy. It ran, but there is a window in my copy of emacs-23.4.1 filled with warnings related to ert.el which indicate that it can't be found. A list of the warnings: Warning (emacs): No ert.el found: not defining test symbol-at-point.2 Warning (emacs): No ert.el found: not defining test symbol-at-point.3 Warning (emacs): No ert.el found: not defining test symbol-at-point.4 Warning (emacs): No ert.el found: not defining test symbol-at-point.5 Warning (emacs): No ert.el found: not defining test symbol-at-point.6 Warning (emacs): No ert.el found: not defining test symbol-at-point.7 Warning (emacs): No ert.el found: not defining test symbol-at-point.9 Warning (emacs): No ert.el found: not defining test symbol-at-point.10 Warning (emacs): No ert.el found: not defining test symbol-at-point.11 Warning (emacs): No ert.el found: not defining test symbol-at-point.12 Warning (emacs): No ert.el found: not defining test symbol-at-point.13 Warning (emacs): No ert.el found: not defining test symbol-at-point.14 Warning (emacs): No ert.el found: not defining test symbol-at-point.15 Warning (emacs): No ert.el found: not defining test symbol-at-point.16 Warning (emacs): No ert.el found: not defining test sexp-at-point.1 Warning (emacs): No ert.el found: not defining test narrowing Warning (emacs): No ert.el found: not defining test find-definition Warning (emacs): No ert.el found: not defining test (find-definition.2 (:fails-for allegro lispworks)) Warning (emacs): No ert.el found: not defining test (find-definition.3 (:fails-for abcl allegro clisp lispworks sbcl ecl)) Warning (emacs): No ert.el found: not defining test complete-symbol Warning (emacs): No ert.el found: not defining test arglist Warning (emacs): No ert.el found: not defining test (compile-defun (:fails-for allegro lispworks clisp ccl)) Warning (emacs): No ert.el found: not defining test (compile-file (:fails-for allegro lispworks clisp)) Warning (emacs): No ert.el found: not defining test utf-8-source Warning (emacs): No ert.el found: not defining test async-eval-debugging Warning (emacs): No ert.el found: not defining test unwind-to-previous-sldb-level Warning (emacs): No ert.el found: not defining test loop-interrupt-quit Warning (emacs): No ert.el found: not defining test loop-interrupt-continue-interrupt-quit Warning (emacs): No ert.el found: not defining test interactive-eval Warning (emacs): No ert.el found: not defining test report-condition-with-circular-list Warning (emacs): No ert.el found: not defining test interrupt-bubbling-idiot Warning (emacs): No ert.el found: not defining test (interrupt-encode-message (:style :sigio)) Warning (emacs): No ert.el found: not defining test inspector Warning (emacs): No ert.el found: not defining test macroexpand Warning (emacs): No ert.el found: not defining test indentation Warning (emacs): No ert.el found: not defining test break Warning (emacs): No ert.el found: not defining test (break2 (:fails-for cmucl allegro ccl)) Warning (emacs): No ert.el found: not defining test locally-bound-debugger-hook Warning (emacs): No ert.el found: not defining test end-of-file Warning (emacs): No ert.el found: not defining test interrupt-at-toplevel Warning (emacs): No ert.el found: not defining test interrupt-in-debugger Warning (emacs): No ert.el found: not defining test flow-control Warning (emacs): No ert.el found: not defining test sbcl-world-lock Warning (emacs): No ert.el found: not defining test (disconnect-one-connection (:style :spawn)) Warning (emacs): No ert.el found: not defining test disconnect-and-reconnect Warning (emacs): No ert.el found: not defining test package-updating Warning (emacs): No ert.el found: not defining test repl-test Warning (emacs): No ert.el found: not defining test (repl-test-2 (:fails-for allegro)) Warning (emacs): No ert.el found: not defining test repl-return Warning (emacs): No ert.el found: not defining test repl-read Warning (emacs): No ert.el found: not defining test repl-read-lines Warning (emacs): No ert.el found: not defining test repl-type-ahead Warning (emacs): No ert.el found: not defining test interrupt-in-blocking-read Warning (emacs): No ert.el found: not defining test move-around-and-be-nasty Warning (emacs): No ert.el found: not defining test form-up-to-point.1 Warning (emacs): No ert.el found: not defining test complete-symbol* Warning (emacs): No ert.el found: not defining test complete-form Warning (emacs): No ert.el found: not defining test font-lock-magic Warning (emacs): No ert.el found: not defining test enclosing-context.1 Warning (emacs): No ert.el found: not defining test find-local-definitions.1 I looked around for a copy of ert.el and ert-x.el and I found a couple of files that looked reasonable, but they won't load so I wonder if you know how to get those files that are compatible with emacs-23.4.1? The github copy of slime seems to load OK, but I haven't really tried using it for development with the warnings I was getting. Thanks in advance, Paul Bowyer

5 8

[Broken] slime/slime#19 (master - 2ea93f5)
by Travis CI 08 Apr '15

08 Apr '15

Build Update for slime/slime ------------------------------------- Build: #19 Status: Broken Duration: 3 minutes and 34 seconds Commit: 2ea93f5 (master) Author: Bozhidar Batsov Message: Highlight README.md's code snippet as Emacs Lisp. View the changeset: https://github.com/slime/slime/compare/e6a51ecff998...2ea93f57c9a4 View the full build log and details: https://travis-ci.org/slime/slime/builds/16431951 -- You can configure recipients for build notifications in your .travis.yml file. See http://about.travis-ci.org/docs/user/build-configuration

4 6

Controlling fasl location
by Paul Bowyer 08 Apr '15

08 Apr '15

Hello Helmut, I found this link on the slime-developer mailing list and I wondered if it is usable and if so, how would I implement it? I don't have a lot of experience fiddling with slime's internals. http://article.gmane.org/gmane.lisp.slime.devel/8378/match=fasl Is there some other convenient way to set the location for fasl files from within a slime session so that when I do a compile/load, the fasl goes to the same location as the output from asdf. Currently the output from asdf goes to one place, and the output from compile/load goes to my source directory. I'm looking for a simple function call that would pass a pathname or would return to the default if no pathname was passed or maybe just a variable that I can set from within a slime session that would do the job. I only want this to to happen for some projects and not happen for others that don't yet use asdf. Thanks, Paul Bowyer

3 8

PATCH: Make slime-snapshot/slime-restore work
by Max Mikhanosha 08 Apr '15

08 Apr '15

Attached patch makes Slime Snapshot contribution work once again. I have tested the following scenarios: 1. M-x slime-snapshot and M-x slime-restore, on a default SBCL build with :spawn communication style 2. Same with dedicated output connection 3. C-u M-x slime-snapshot (saves in the background) 4. Restoring snapshot saved with different value of *use-dedicated-output-stream* 5. Save and restore snapshot without 'slime-repl loaded 6. All of the above re-tested on a single-threaded SBCL build, with :fd-handler communication style Details of the implementation: 1. Because SBCL can not fork() with multiple-threads running, patch introduce a new mechanism called "Thread Stopper". It has single entry point, SWANK:REGISTER-THREAD-STOPPER which adds a callback, called by SWANK to stop/start background threads of various libraries. 2. A new entry point SWANK:CALL-WITH-ONLY-INITIAL-THREAD will stop all background threads (using the above thread stopper protocol), except for the initial thread in the Lisp image, and restart them 3. Swank itself uses the thread stopper protocol, to register a callback that will stop all the multithreaded connections threads, and then restart them after the call to fork() 4. In the implementation of the above, there were several swank-backend interface changed, and some added, namely MAKE-FD-STREAM had gained element-type argument, backend JOIN-THREAD added, and CREATE-REPL had new keyword argument added. The thread stopper interface is intentionally minimalist, with a single entry point, as to simplify adding thread-stopper hooks to libraries, they can dispatch on (fboundp) or such. Regards, Max

1 2

Proposed tweak for `slime-lisp-options'
by Mirko Vukovic 08 Apr '15

08 Apr '15

Hi, `slime-lisp-options' in slime.el uses `split-string' to parse the contents of `inferior-lisp-program' This fails if the lisp program is in a path with spaces in it (such as executables in Windows). Quoting does not help. One could instead use split-string-and-unquote: (split-string-and-unquote "\"c:/Program Files (x86)/clisp-2.49/clisp.exe\" -E iso-8859-1") ("c:/Program Files (x86)/clisp-2.49/clisp.exe" "-E" "iso-8859-1") Mirko

3 3

Segmentation fault on Raspberry pi
by Christer Enfors 08 Apr '15

08 Apr '15

Greetings! I'm trying to run SLIME on a Raspberry pi (a USD 35 computer), but it seems CLisp crashes when I try to start SLIME: ===CUT=== (progn (load "/usr/share/common-lisp/source/slime/swank-loader.lisp" :verbose t\ ) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "\ swank:start-server") "/tmp/slime.9481")) i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I \ `+' / I 8 8 8 8 8 8 \ `-+-' / 8 8 8 ooooo 8oooo `-__|__-' 8 8 8 8 8 | 8 o 8 8 o 8 8 ------+------ ooooo 8oooooo ooo8ooo ooooo 8 Welcome to GNU CLISP 2.49 (2010-07-07) <http://clisp.cons.org/> Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2010 Type :h and hit Enter for context help. [1]> ;; Loading file /usr/share/common-lisp/source/slime/swank-loader.lisp ... ;; Loading file /usr/share/common-lisp/source/cl-asdf/asdf.lisp ... *** - handle_fault error2 ! address = 0x369564a4 not in [0x1ab8c000,0x1acda7c0)\ ! SIGSEGV cannot be cured. Fault address = 0x369564a4. GC count: 0 Space collected by GC: 0 0 Run time: 0 500000 Real time: 1 281123 GC time: 0 0 Permanently allocated: 90368 bytes. Currently in use: 2422148 bytes. Free space: 4 bytes. Process inferior-lisp segmentation fault ===CUT=== Seems to me like it's running out of memory, which is surprising considering the Raspberry pi has 512 MB RAM, oodles of which is free: ===CUT=== enfors@raspberrypi /etc $ free total used free shared buffers cached Mem: 448736 357180 91556 0 26416 291876 -/+ buffers/cache: 38888 409848 Swap: 102396 0 102396 enfors@raspberrypi /etc $ ===CUT=== (In case the formatting looks off on your display, it has 91 MB free RAM, 409 MB if you don't count buffers). Other information: Operating system: Latest version of Raspberian (based on Debian, I believe) CLisp implementation: GNU CLISP version 2.49 Emacs version: 23.4.1 I'm not sure how to extract SLIME's version number, but it's the one that came with Emacs. Any help is greatly appreciated. -- Christer Enfors

3 5

Patch for LispWorks compiler notes error
by Robert Smith 08 Apr '15

08 Apr '15

Hello: As it stands, SLIME will error when it encounters compiler notes generated by LispWorks 6 :EXPLAIN functionality. For example: (defun dist (x y) (declare (:explain :variables)) (sqrt (+ (* x x) (* y y)))) will error with #<CONDITIONS:COMPILER-NOTE 402026DC23> fell through ETYPECASE expression. Wanted one of (ERROR STYLE-WARNING WARNING). [Condition of type CONDITIONS:CASE-FAILURE] As a patch, add the two lines prefixed by a + to the function LISPWORKS-SEVERITY in the file "swank-lispworks.lisp" indicated at the end of this mail. Thanks, Robert PATCH FOR "swank-lispworks.lisp": (defun lispworks-severity (condition) (cond ((not condition) :warning) (t (etypecase condition + #+lispworks6 + (conditions:compiler-note :note) (error :error) (style-warning :warning) (warning :warning)))))

2 1

Re: [slime] the inspector doesn't run the swank side in the initiating thread (#12)
by Helmut Eller 08 Apr '15

08 Apr '15

On Sat, Jan 04 2014, João Távora wrote: > Helmut Eller <notifications(a)github.com> writes: > >> On Fri, Jan 03 2014, João Távora wrote: >> >>> In any case we should reopen the issue and mark it low priority. It >>> would make nice a feature, whatever the implementation. >> I consider this bloat and not a valuable feature. > > Helmut, > > I assigned the issue to me and reopened it. At the end of this message I > explain what I intend to do with it, and will not do any rogue commit or > anything. > > I really think we should not close off such feature requests with > statements of personal preference. While stating opinion is of course > OK, closing discussions out of view not only doesn't make the demand go > away, but detracts from one of the advantages of the github ecosystem > which is attracting hackers that might be willing to do Slime "the > sincerest form of code appreciation". OK, as you wish. > Given the conditions we're in (daily hungry SLIME users), as Luís > explained, we are committed to inverting the effective dev stall that > Slime has seen in the past years (lately completely dead). We went to > some lengths to refrain from forking and keep the general project > policies. > > I think it's only fair to list at least approximately my personal goals > for the project: > > * All current slime tests should pass in various combinations (this is > being worked on currently). > > * Slime should be installable via ELPA and el-get > > * Contribs should be completely independent (no need to add their swank > files to *CONTRIBS*) and also installable via ELPA and el-get, which > both manage dependencies nicely. > > * Modern emacs coding conventions should be adhered to. This sounds all good. > I'd also like hear your (and everyone else's) plans for the future of > Slime. My goals are: * keep maintance effort down, i.e. I don't want to spend my time or have endless discussions on features that I don't actually use * make it easier for other people to create and cooperate on contribs or features that they care about but are of limited interest to me or the average SLIME user * continued support for Emacs 23. Using the Emacs version that is in Debian Stable should be as hassle-free as possible. * There are always some cleanups to do, e.g. the CMUCL backend should finally use Gray streams. * for the dedicated output stream it would be reasonable to keep the initial port open to avoid some firewall issues. That would also make it easy to open other sockets, which is much more likely to fly than the idea with multiplexed streams on a single connection. * I would like to compile my Lisp code with makefiles. Maybe SLIME could ship some command line tools to make that easier. This may be outside the scope of SLIME, tho. > Reading through slime.el I agree with you that it is indeed a bit > bloated. I'm also commited to cleaning it up. By offloading tests to > ert.el for example I relieved slime of 250 lines of test framework. If > you look at the diffs you'll see other small refactorings. Yes, that was good work. > So while I think the patch at hand is hardly bloat (because of its small > size), I also agree that Slime's core should grow smaller and offer more > consistent interfaces so features like the one requested by Attila can > be implemented as contribs. Lets keep this issue open as an attempt to > do that, who knows, you might be surprised with less and more > maintainable lines of code instead of more. That would indeed be a surprise. Helmut

1 0

New contrib: slime-trace-dialog
by joaotavora＠gmail.com 08 Apr '15

08 Apr '15

Hello, I submit for review a new contrib I've been working on, an interactive dialog for examining the tree of collected traces. It's inspired by Allegro's trace dialog. Here's a screenshot: http://i.imgur.com/ycIzzOf.png It's probably still a little rough around the edges, but is proving really useful for my work, and integrates well with the rest of slime. The best way to understand how it works is to try it out: * apply the patch attached to any recent slime * point a git slime to the "slime-trace-dialog" branch at http://github.com/capitaomorte/slime slime-trace-dialog is automatically loaded by the slime-fancy contrib: * specs are traced/untraced with C-c M-t, works like C-c C-t * open the dialog with C-c T, or M-x slime-trace-dialog * click on the interactive parts of the dialog, to control trace collection and inspect objects. It needs emacs 24 for its lexical-binding feature. I've tested with sbcl, allegro, and clisp. The swank-side of the contrib, swank-trace-dialog.lisp, uses a new group of interfaces in swank-backend.lisp, WRAP, UNWRAP and WRAPPED-P. There is a default implementation for each one, but the allegro implementation is best, and allows tracing of complex specs using the slime-fancy-trace contrib. sbcl's implementation is second best. I added these interfaces so they can assist in writing future extensions, like maybe a simple interactive profiler. Thanks, João

2 4

Testing subscriber post
by Drew C 08 Apr '15

08 Apr '15

This should simply go through non-moderated. -- drewc

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
424
Older →

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