slime-devel November 2003

slime-devel@common-lisp.net

27 participants
57 discussions

[slime-devel] Problem compiling functions longer than around 4093 characters?
by Fred Gilham 07 Nov '03

07 Nov '03

Hello, I was trying to compile a function interactively (i.e. with ^C^C). It's a relatively long function. When I did it under slime, I got the following: * ;; Connection to Emacs lost. ;; [ Error in function LISP::ASSERT-ERROR: Short read: length=4191 pos=4093] The function uses XLIB and I shortened it by "using" XLIB and changing the xlib:<foo> calls to just <foo> calls. It then compiled without error. So I looked around and found another piece of code with a long function. It is over 10000 characters. The same thing happened: * ;; Connection to Emacs lost. ;; [ Error in function LISP::ASSERT-ERROR: Short read: length=13988 pos=4093] The error occurs in read-next-form in swank.lisp. Looks like the code isn't handling the transfer of more than one pipe-buffer-full of data. I'm using a very recent slime. -- Fred Gilham gilham(a)csl.sri.com Behold, how good and pleasant it is when brothers dwell in unity. It is like the precious oil upon the head, running down upon the beard, upon the beard of Aaron, running down on the collar of his robes. It is like the dew of Hermon, which falls on the mountains of Zion. For there the LORD has commanded the blessing, life for evermore. -Ps 133

2 1

[slime-devel] [PATCH] add eldoc support (take 2)
by Sean O'Rourke 06 Nov '03

06 Nov '03

Take 2 on adding eldoc support to SLIME. Things to note: - support for GNU version >= 21.3 using hook ``eldoc-print-current-symbol-info-function''; older versions use advice. - 2 approaches to caching arglist lookups; see variable ``slime-cache-type'' for details. - avoids interning symbols when looking for functions that don't exist. - function ``slime-documentation'' to display documentation rather than description for thing-at-point. Try it out! Comments welcome. /s

3 3

[slime-devel] slime-buffer-package not getting set in *slime-repl*
by William C. Halliburton 06 Nov '03

06 Nov '03

I noticed that the function completions while in a package in *slime-repl* were not correct. It seems that slime-find-buffer-package does not work for the repl. Looks like the regex wants it at the beginning of the line. Now sync-package-and-default-directory works in the repl because it calls swank:set-package with NIL which returns the current package. I changed sync-package-and-default-directory to be (defun slime-sync-package-and-default-directory () (interactive) (let ((package (slime-eval `(swank:set-package ,(slime-find-buffer-package)))) (directory (slime-eval `(swank:set-default-directory ,(expand-file-name default-directory))))) (setq slime-buffer-package package) ;;; <----- added this line (message "package: %s default-directory: %s" package directory))) Which works for my purposes but may not be the best way. Thanks, William Halliburton

2 1

[slime-devel] SLIME/SBCL bug
by Raymond Wiker 05 Nov '03

05 Nov '03

A few things: 1) How do I subscribe to slime-devel? I'm not sure that I have anything to contribute, but I like knowing what's going on :-) 2) swank-sbcl does (require 'sb-bsd-sockets) and (require 'sb-introspect) These are asdf packages, and require won't be able to find them unless asdf itself is in the SBCL image; in other words, they should be preceded by (require 'asdf) 3) I've been seeing these errors (or something similar) for a few days now: : You have encountered a bug in SLIME. : : The communication state machine received an event that was illegal for : its current state, which means that the communication between Emacs : and Lisp has lost synchronization. The connection to Lisp has : therefore been closed. : : You can open a fresh connection with `M-x slime'. : : Please report this problem to your friendly neighbourhood SLIME : hacker, or the mailing list at slime-devel(a)common-lisp.net. Please : include in your report: : : A description of what you were doing when the problem occured, : the version of SLIME, Emacs, and Lisp that you are using, : the Lisp backtrace, if one was printed, : and the information printed below: : : The event was: : (:new-features : ("ASDF" "ANSI-CL" "COMMON-LISP" "SBCL" "UNIX" "SB-DOC" "SB-TEST" "IEEE-FLOATING-POINT" "X86" "BSD" "FREEBSD" "GENCGC" "STACK-GROWS-DOWNWARD-NOT-UPWARD" "C-STACK-IS-CONTROL-STACK")) : : : The state stack was: : (slime-evaluating-state slime-idle-state)

2 2

[slime-devel] [PATCH] add eldoc support
by Sean O'Rourke 04 Nov '03

04 Nov '03

This patch lets SLIME support Eldoc (i.e. flashing argument lists in the minibuffer). Inspired by semantic/cedet, which does this for many languages. /s --- slime.el.~1.61.~ Wed Oct 29 17:18:24 2003 +++ slime.el Sat Nov 1 18:06:03 2003 @@ -1771,20 +1771,40 @@ (slime-function-called-at-point/line)) (slime-arglist (symbol-name (slime-function-called-at-point/line))))) -(defun slime-arglist (symbol-name) +(defvar slime-arglist-cache (make-hash-table :test 'equal) + "Cache for Slime arglist info (useful with Eldoc).") + +(defun slime-arglist (symbol-name &optional show) "Show the argument list for the nearest function call, if any." (interactive (list (slime-read-symbol "Arglist of: "))) - (slime-eval-async - `(swank:arglist-string ,symbol-name) - (slime-buffer-package) - (lexical-let ((symbol-name symbol-name)) - (lambda (arglist) - (message "%s" (slime-format-arglist symbol-name arglist)))))) + (unless show + (setq show #'message)) + (let ((val (gethash symbol-name slime-arglist-cache))) + (if val + (funcall show "%s" val) + (slime-eval-async + `(swank:arglist-string ,symbol-name) + (slime-buffer-package) + (lexical-let ((symbol-name symbol-name)) + (lambda (arglist) + (funcall show "%s" + (setf (gethash symbol-name slime-arglist-cache) + (slime-format-arglist symbol-name arglist))))))))) (defun slime-get-arglist (symbol-name) "Return the argument list for SYMBOL-NAME." - (slime-format-arglist symbol-name - (slime-eval `(swank:arglist-string ,symbol-name)))) + (or (gethash symbol-name slime-arglist-cache) + (setf (gethash symbol-name slime-arglist-cache) + (slime-format-arglist symbol-name + (slime-eval `(swank:arglist-string ,symbol-name)))))) + +(defadvice eldoc-print-current-symbol-info (around slime activate) + "Enable Eldoc argument list feedback with SLIME/SWANK." + (if (eq major-mode 'lisp-mode) + (let ((sym (slime-function-called-at-point/line))) + (when sym + (slime-arglist (symbol-name sym) #'eldoc-message))) + ad-do-it)) (defun slime-format-arglist (symbol-name arglist) (format "(%s %s)" symbol-name (substring arglist 1 -1)))

3 2

[slime-devel] swank.lisp 1.50 breaks Slime
by Johannes Groedem 02 Nov '03

02 Nov '03

Version 1.49 works fine, but 1.50 (and 1.51) gives me this when I start Slime: ---8<--- (From *Messages* and the Slime-repl:) Polling "/tmp/slime.8009".. (Abort with `M-x slime-disconnect'.) [2 times] Connecting to Swank on port 41288.. Disconnected. error in process filter: slime-state/event-panic: The SLIME protocol reached an inconsistent state. error in process filter: The SLIME protocol reached an inconsistent state. The event was: (:new-features ("ASDF" "MK-DEFSYSTEM" "COMMON-LISP-CONTROLLER" "PCL-STRUCTURES" "PORTABLE-COMMONLOOPS" "PCL" "PYTHON" "PENTIUM" "I486" "LINKAGE-TABLE" "MP" "GENCGC" "CMU18" "CMU18E" "RELATIVE-PACKAGE-NAMES" "CONSERVATIVE-FLOAT-TYPE" "RANDOM-MT19937" "HASH-NEW" "X86" "LINUX" "GLIBC2" "UNIX" "COMMON" "CMU" "NEW-COMPILER" "COMMON-LISP" "ANSI-CL" "IEEE-FLOATING-POINT")) The state stack was: (slime-evaluating-state slime-idle-state) ---8<--- This is with Emacs 21.3+1-4 and CMUCL 18e-7 on Debian. -- Johannes Groedem <OpenPGP: 5055654C>

3 4

[slime-devel] REPL mode
by Helmut Eller 02 Nov '03

02 Nov '03

Hi, I've committed the beginnings of a comint-less REPL. Here are some thoughts. This is a proof of concept, to see if our own REPL is actually better than the (not-so-) inferior-lisp mode. The REPL is activated in the in idle-state and shares the buffer with the other (redirected) output. Some markers track the prompt, the user input, and the beginning of the output. The current design doesn't maintain any state on the Lisp side (we probably should do that, e.g., for things like *, **, *** etc.). Some not so nice things about the new REPL: - since I didn't use comint I had to implement the history management myself. - prompting is triggered by the activation event of the idle state. This means the prompt is printed before we can print the result and we have to go back and insert the result before the prompt. Also we have to check on every idle-state activation event, if we actually need insert a prompt (to avoid many unneeded prompts). - slime-space can produce output and cause a new prompt. This can happen when CMUCL emits warnings during the first coercion a symbol to a function. There is currently no good input handling, e.g, when the Lisp side calls read-char on the redirected input stream, Emacs just reads a line from the minibuffer. My plan was to switch the keymap in the repl buffer when the Lisp side request input. The other keymap doesn't behave like a repl, but send the input more or less uninterpreted to the Lisp side. Not sure how to implement this though. Since I'm not using the repl all that much I'm not sure if it is worth the trouble. There are also problems with output buffering, e.g., when you evaluate (labels ((foo () (foo) t)) (foo)) in the listener, CMUCL puts you in the (tty-) debugger, but you can't see it because the output is buffered somewhere. The nicest thing about this repl is the integration with our debugger. The ugliest thing is the complexity that is needed for better input redirection. Helmut.

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel November 2003