slime-devel June 2016

slime-devel@common-lisp.net

4 participants
4 discussions

slime-edit-definition doesn't lookup the definition at point
by Chaitanya Gupta 26 Jun '16

26 Jun '16

In my Lisp buffer, when the point is over a symbol and I press M-. (slime-edit-definition), I get the following error: cl-assoc: Symbol's function definition is void: equalp If the point is over some whitespace, then things work as expected: M-. gives me the "Edit Definition of" prompt in the minibuffer and looks up the correct definition. I guess I can define equalp in my .emacs to fix this, but I would prefer if it worked out of the box. I am using GNU Emacs 24.5.1 and SLIME 20160624.851 (installed from melpa). Chaitanya

1 1

Slime: arithmetic error COMMON-LISP:FLOATING-POINT-INVALID-OPERATION signalled
by David Hodge 22 Jun '16

22 Jun '16

Slime Version: 2.18 SBCL Version: 1.3.3 Having recently upgraded SBCL I pulled the latest quicklisp version of slime as well. I now get this error message popping up at random, but frequent intervals. It usually happens as I am typing at the REPL. I wonder if anyone might comment on what is happening - I can accept its my environment, but am at a loss as to how to track it down. Cheers The back trace is provided below: 0: ("bogus stack frame") 1: ("foreign function: maybe_now_maybe_later") 2: ("foreign function: _sigtramp") 3: ("foreign function: #x100B4A3F13") 4: (COMMON-LISP:FIND-SYMBOL "OR" #<COMMON-LISP:PACKAGE "SWANK-IO-PACKAGE">) 5: (SB-IMPL::OUTPUT-SYMBOL COMMON-LISP:OR #<SB-IMPL::STRING-OUTPUT-STREAM {100B4A6943}>) 6: ((COMMON-LISP:LABELS SB-IMPL::HANDLE-IT :IN SB-KERNEL:OUTPUT-OBJECT) #<SB-IMPL::STRING-OUTPUT-STREAM {100B4A6943}>) 7: (SB-IMPL::OUTPUT-LIST (COMMON-LISP:OR (:EMACS-REX . SWANK::_) (:EMACS-CHANNEL-SEND . SWANK::_)) #<SB-IMPL::STRING-OUTPUT-STREAM {100B4A6943}>) 8: ((COMMON-LISP:LABELS SB-IMPL::HANDLE-IT :IN SB-KERNEL:OUTPUT-OBJECT) #<SB-IMPL::STRING-OUTPUT-STREAM {100B4A6943}>) 9: (COMMON-LISP:PRIN1 (COMMON-LISP:OR (:EMACS-REX . SWANK::_) (:EMACS-CHANNEL-SEND . SWANK::_)) #<SB-IMPL::STRING-OUTPUT-STREAM {100B4A6943}>) 10: (SB-FORMAT::S-FORMAT-DIRECTIVE-INTERPRETER #<SB-IMPL::STRING-OUTPUT-STREAM {100B4A6943}> #<~s> (" " #<~s> #<~%>) #<unavailable argument> #<unavailable argument>) 11: (SB-FORMAT::INTERPRET-DIRECTIVE-LIST #<SB-IMPL::STRING-OUTPUT-STREAM {100B4A6943}> (#<~s> " " #<~s> #<~%>) ((COMMON-LISP:OR # #) T) ((COMMON-LISP:OR # #) T)) 12: (SB-FORMAT::%FORMAT #<SB-IMPL::STRING-OUTPUT-STREAM {100B4A6943}> "wait-for-event: ~s ~s~%" ((COMMON-LISP:OR # #) T) ((COMMON-LISP:OR # #) T)) 13: ((COMMON-LISP:LAMBDA NIL :IN SWANK::LOG-EVENT)) 14: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (COMMON-LISP:LAMBDA NIL :IN SWANK::LOG-EVENT) {100B4A680B}>) 15: (SWANK/SBCL::CALL-WITH-BREAK-HOOK #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL :IN SWANK::HANDLE-REQUESTS) {100B67322B}>) Locals: CONTINUATION = #<CLOSURE (LAMBDA () :IN SWANK::HANDLE-REQUESTS) {100B67322B}> HOOK = #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> 16: ((FLET SWANK/BACKEND:CALL-WITH-DEBUGGER-HOOK :IN "/Users/dbh/quicklisp/dists/quicklisp/software/slime-v2.18/swank/sbcl.lisp") #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL :IN SWANK::HAN.. 17: (SWANK::CALL-WITH-BINDINGS ((*STANDARD-INPUT* . #1=#<SWANK/GRAY::SLIME-INPUT-STREAM {100CFA82E3}>) (*STANDARD-OUTPUT* . #2=#<SWANK/GRAY::SLIME-OUTPUT-STREAM {100D07A0A3}>) (*TRACE-OUTPUT* . #2#) (*ERR.. 18: (SWANK::HANDLE-REQUESTS #<SWANK::SINGLETHREADED-CONNECTION {100C38F373}> T) 19: (SWANK::INVOKE-OR-QUEUE-INTERRUPT #<CLOSURE (LAMBDA NIL :IN SWANK::PROCESS-IO-INTERRUPT) {100B67292B}>) 20: (SWANK::PROCESS-IO-INTERRUPT #<SWANK::SINGLETHREADED-CONNECTION {100C38F373}>) 21: (SWANK/SBCL::SIGIO-HANDLER #<unused argument> #<unused argument> #<unused argument>) 22: ((FLET #:WITHOUT-INTERRUPTS-BODY-44 :IN SB-SYS:INVOKE-INTERRUPTION)) 23: ((FLET SB-THREAD::EXEC :IN SB-SYS:INVOKE-INTERRUPTION)) 24: ((FLET #:WITHOUT-INTERRUPTS-BODY-35 :IN SB-SYS:INVOKE-INTERRUPTION)) 25: (SB-SYS:INVOKE-INTERRUPTION #<CLOSURE (FLET SB-UNIX::INTERRUPTION :IN SB-SYS:ENABLE-INTERRUPT) {A1FEB5B}>) 26: ((FLET SB-UNIX::RUN-HANDLER :IN SB-SYS:ENABLE-INTERRUPT) 23 #.(SB-SYS:INT-SAP #X0A1FF168) #.(SB-SYS:INT-SAP #X0A1FF1D0))

1 0

Playing nice with custom repls?
by Zach Beane 15 Jun '16

15 Jun '16

I like writing specialized little repls sometimes, with syntax optimized for a specific task. When I'm in a repl like that, slime drops many useful features, like M-., arglist display in file buffers, etc. Is there a way to have those features still work even when I'm in my own repl? Thanks, Zach

2 4

Source location improvements for Allegro CL >= 10.0
by Luís Oliveira 12 Jun '16

12 Jun '16

Hello, Allegro CL 10.0 features improved source location information for compiler warnings: whereas previously warnings were associated with the top-level form where they occur, now we can pinpoint the offending subform. I've just pushed some code to the master branch that takes advantage of this enhanced information. (screenshot: http://imgur.com/pe6Bw20) Feedback from Allegro users is welcome! Cheers, Luís

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel June 2016