slime-devel April 2015

slime-devel@common-lisp.net

63 participants
80 discussions

Warnings and compile failures
by Zach 08 Apr '15

08 Apr '15

List, It seems that when Slime encounters a warning during compilation, it reports the compilation as a failed and the defuns are not updated. Is there a way to disable this for decidedly benign warnings? If you care for context, Iterate warns if you include some code that it cannot walk. I want to iterate over something wrapped in a without-interrupts environment (some C code, which doesn't handle interruptions well). Without-interrupts, in SBCL, uses a macrolet environment which is one of the things that the Iterate code walker doesn't know how to walk. That said, the inability to walk the code in no way affects the execution unless there are forms in the unwalkable code that are Iterate directives (or whatever you want to call them). This means that so long as there Slime aborts compilation upon any warning, any code with a macrolet inside an Iterate is more difficult than than it needs to be when compiling from a buffer in Slime. I am now wrapping the offending macrolet code in another function call so Iterate doesn't know about it and doesn't complain, but it would be nice if these kinds of work-arounds weren't necessary. Thanks, Zach KS

3 2

Slime not connecting to swank socket
by Dana Wheeler 08 Apr '15

08 Apr '15

When starting slime with "M-x slime" a window is created and displays the *inferior-lisp* process with the message: (progn (load "/Users/Dana/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/var/folders/gq/3hr2_3j961d6rsz4dm8x83ch0000gq/T/slime.2310")) and polls ... forever. Enmap 127.0.0.1 shows 4005/tcp open pxc-pin so swank appears to be working and has opened the proper port but ls /var/folders/gq/<gobbldee-goop>/T shows no file "slime.2310". I am assuming that slime made a request to the system for a virtual file interface to the port 127.0.0.1:4005 and that request failed either on the slime end or the system end. Setting M-x toggle-debug-on-error produces no information as apparently emacs hasn't detected an error. The slime portion of my configuration is ;; *************************** Activate SLIME for Clozure ******************************* (add-to-list 'load-path "/Users/Dana/slime/") ; your SLIME directory (setq inferior-lisp-program "/Applications/ClozureCL.app/Contents/MacOS/dx86cl64 -K utf-8") (require 'slime) (slime-setup) Any suggestions on how to debug this would be greatly appreciated. Software: OS X 10.7.5 Clozure 1.8.1 (15418) Emacs 24.3 (9.0) Slime cvs version downloaded 2013-09-14 Thanks Dana S. Wheeler dswheeler777.at.gmail.com

2 2

slime-sexp-at-point in slime-repl buffers
by Marco Baringer 08 Apr '15

08 Apr '15

Calling slime-inspect at a prompt in the slime repl buffer without any other input will suggest the prompt itself ("CL-USER>" or whatever) as the default value to inspect. I can not think of any case where this behaviour would be useful :) The attached patch advises slime-sexp-at-point, when the slime-repl.el contrib is loaded, to ignore the prompt text (if point is in the input area, otherwise the normal behaviour of slime-sexp-at-point applies). Unless anyone objects to the patch (or the implementation) i'll commit this later tomorrow. -- -marco

3 5

[slime-devel] SLIME talk at the Emacs Conference
by Luke Gorrie 08 Apr '15

08 Apr '15

Howdy! Long time no chat :-) I will give a talk at the Emacs Conference (emacsconf.org, London March 31) called "How to write an Emacs-based IDE like SLIME". The idea is to demo SLIME, explain how its development works, and give some encouragement and practical tips to people who might want to build something similar for other languages. If you have some ideas please fire away :) particularly about things I might easily overlook being as my SLIME know-how is about 10 years old! Cheers, -Luke

2 2

Re: Freeze for SLIME 2.4
by Paul Bowyer 08 Apr '15

08 Apr '15

On 02/23/2014 12:10 PM, Luís Oliveira wrote: > On Sun, Feb 23, 2014 at 6:02 PM, Paul Bowyer <pbowyer(a)olynet.com> wrote: >> The first is : >> Loading tramp...done >> funcall: Symbol's function definition is void: tramp-init >> >> I disabled slime-tramp in my .emacs file. > Works for me. Can you show me how you were enabling slime-tramp? I'm attaching a copy of my .emacs file renamed to my_dot_emacs. There will be changes to my .emacs as I learn more about what I need. > > >> The second is: >> Loading /home/pfb/my-slime-sandbox/slime/contrib/slime-cl-indent.el >> (source)...done >> slime-enclosing-context-init: This contrib does not work at the moment. >> >> This is a dependency of: >> slime-mdot-fu >> >> I disabled slime-mdot-fu in my .emacs file. > This contrib appears to have been broken for a very long time. I've > created an issue for it: <https://github.com/slime/slime/issues/111>. >

2 3

[patch] another fix for find-definition in the REPL buffer
by João Távora 08 Apr '15

08 Apr '15

I found and fixed another annoyance when trying to M-. on a presentation in the REPL buffer with the slime-fancy contrib enabled. This appears to be traceable to the slime-presentations contrib, so I'm cc'ing the authors The function I changed must return nil on failure so as not to break the `run-hooks-until-success' logic of `slime-edit-definition-hooks'. diff --git a/contrib/slime-presentations.el b/contrib/slime-presentations.el index a462669..fd0fd63 100644 --- a/contrib/slime-presentations.el +++ b/contrib/slime-presentations.el @@ -401,11 +401,12 @@ Also return the start position, end position, and buffer of the presentation." (location (slime-eval `(swank:find-definition-for-thing (swank:lookup-presented-object ',(slime-presentation-id presentation)))))) + (unless (eq (car location) :error) (slime-edit-definition-cont (and location (list (make-slime-xref :dspec `(,presentation-string) :location location))) presentation-string - where))) + where)))) BTW, I wonder if providing these patches with full changelog and ready to commit would somehow speed up the analysis/integration -- João Távora

2 4

SLIME and Quicklisp
by Zach Beane 08 Apr '15

08 Apr '15

Each month I take a snapshot of SLIME from CVS and include it in Quicklisp. When development was slow, this rarely resulted in broken versions. Now that development has moved to git and picked up speed, I'm concerned about including a version of SLIME that might have some temporary brokenness. Can you recommend a way to raise the odds that Quicklisp uses a very good version of SLIME? Zach

3 6

Fwd: Patch for customizing Allegro temp file and directory
by Dave Cooper 08 Apr '15

08 Apr '15

Dear Slime Maintainers, Please consider applying the attached patch, which affects swank-allegro.lisp and allows customization of the temporary directory for Allegro CL. It turns out that Allegro's (system:temporary-directory) [which is the default directory used by system:make-temp-file-name] can sometimes get confused on Windows in situations such as with certain network filesystem configurations. We will follow up with Franz to understand in more detail what can cause the confusion, but in any case I think it will be useful to be able to customize the location of Slime's temporary files without modifying Slime sources. -- My Best, Dave Cooper, Genworks Support

4 5

how to specify the readtable to be used when swank is handling request from slime
by Anton Vodonosov 08 Apr '15

08 Apr '15

When you work with SLIME and your code depends on customized readtable, how do you ensure slime requests are handled with your readtable? I mean for example in CCL, when :span communication style is used by SLIME each requests is handled by new thread and new threads are initialized with default value of cl:*readtable*. In my source code I have (eval-when (:compile-toplevel :load-toplevel :execute) (when (find-package :swank) (eval (read-from-string "(push `(*readtable* . ,*readtable*) swank:*default-worker-thread-bindings*)")))) but I am afraid it is not the conventional way and depends on swank being already loaded at the moment my code is loaded. What is the better way? Best regards, - Anton

4 7

Re: slime on github
by Paul Bowyer 08 Apr '15

08 Apr '15

On 01/10/2014 11:24 AM, João Távora wrote: > Paul Bowyer <pbowyer(a)olynet.com> writes: >>>> As a suggestion, the documentation should also be upgraded to reflect the change >>>> to github and any other new features that are added. >>> Yes. I reworked the setup instructions (and reworked the `slime-setup' >>> mechanism slightly), have a look at the new README in the github home >>> page and try it out. >> I was referring to the manual that is in the slime/doc folder, which still >> contains all the CVS instructions for downloading slime. I keep the slime manual >> handy for reference. Sorry I didn't make myself clear in my last >> message. > Oh, you're right, that needs updating too. > > We'll make updating the texinfo manual a prerequisite for the next > release. I'm afraid we won't be able to update your existing printed > copy though :-) > >>> Still, the trunk might always contain some instability, in those cases >>> do fallback to the last tag and report those bugs in the issue >>> tracker. We'll try to sort out a release strategy as soon as possible. >> I did notice some problems in the master branch, so I checked out SLIME_2 and >> used that. > Care to describe them? I'd be very insterested. I get several messages when I start slime after checking out the master branch. Connecting to Swank on port 34085.. error in process filter: slime-for-each-presentation-in-region: Invalid function: (handle-presentation (presentation point) (multiple-value-bind (start end whole-p) (slime-presentation-bounds point presentation object) (funcall function presentation start end whole-p))) error in process filter: Invalid function: (handle-presentation (presentation point) (multiple-value-bind (start end whole-p) (slime-presentation-bounds point presentation object) (funcall function presentation start end whole-p))) That was not the case yesterday, but this morning I downloaded slime again thinking that the manual may have been updated and now I get the messages when I start slime. I also get similar messages when I use "repl>clear buffer" menu item. > > João >

4 16

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel April 2015