slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] New bug in M-. ?
by Jeffrey Cunningham 25 Nov '06

25 Nov '06

I don't know when this crept in, but currently whenever I press M-. on a function which is part of CL (e.g. 'file-size 'rename-file) slime and emacs crash. Emacs won't even refresh its windows and I have to kill its process and restart. But it works just fine on local package functions. I'm running CMUCL 19d with slime out CVS yesterday on a Gentoo box. --Jeff

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 24 Nov '06

24 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1006 slime/ChangeLog:1.1007 --- slime/ChangeLog:1.1006 Thu Nov 23 18:14:37 2006 +++ slime/ChangeLog Fri Nov 24 18:34:58 2006 @@ -1,3 +1,9 @@ +2006-11-25 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-repl-read-break): Use a :emacs-interrupt message + instead of a RPC to swank:simple-break. Suggested by Taylor R + Campbell. + 2006-11-24 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-search-buffer-package): Prettify the package

1 0

[slime-devel] interrupt vs simple-break
by Taylor R Campbell 24 Nov '06

24 Nov '06

Can someone explain to me the purpose of distinguishing the :EMACS-INTERRUPT wire message from the SWANK:SIMPLE-BREAK RPC, or why `slime-repl-read-break' on the Emacs side sends an :EMACS-REX of the latter rather than just sending an :EMACS-INTERRUPT message?

2 4

Re: [slime-devel] Re: SLIME Committers
by Edi Weitz 24 Nov '06

24 Nov '06

On Tue, 21 Nov 2006 08:36:53 -0800, Jeffrey Cunningham <jeffrey(a)cunningham.net> wrote: > On Tue Nov 21, 2006 at 08:12:44AM +0100, Edi Weitz wrote: >> >> Does usage of plain old CVS hold back SLIME development in any way? >> > Many big companies have their firewalls set up to block the port CVS > uses - I've been told the MSEE training their IT people get tells > them to do this. That means you can't grab CVS versions of Slime > behind these firewalls. If you just want the current CVS version to /use/ SLIME, you can get it through http, of course: http://common-lisp.net/cgi-bin/viewcvs.cgi/root.tar.gz?root=slime&view=tar But, yes, if you actually want to work on SLIME and submit code, this might be a problem. Does anyone know how many active developers we have who are paid by their big company employers to hack SLIME during their working hours? :) But wait, project members use CVS via ssh, don't they? So, if the CVS port is blocked, that shouldn't be problem. > I assume I'm not alone with this problem. > > Darcs just works. For some people... :)

10 11

[slime-devel] open parenthesis in the documentation string confuses slime-compile-defun
by Anton Vodonosov 24 Nov '06

24 Nov '06

Open parenthesis in the documentation string confuses slime-compile-defun. Exmaple: (defun f2 () " ( ... ) " ) Note, open parenthesis shuld be the first character of the line. Trying to compile this with slime-compile-defun signals the following: READ from #1=#<INPUT STRING-INPUT-STREAM>: a token consisting only of dots cannot be meaningfully read in [Condition of type SYSTEM::SIMPLE-READER-ERROR] Looks like on the emacs side slime takes this open parenthesis into account when picking out parentheses-balanced portion of text. Regards, -Anton

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 23 Nov '06

23 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1005 slime/ChangeLog:1.1006 --- slime/ChangeLog:1.1005 Wed Nov 22 10:29:23 2006 +++ slime/ChangeLog Thu Nov 23 18:14:37 2006 @@ -1,3 +1,18 @@ +2006-11-24 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-search-buffer-package): Prettify the package + name if it is written as string or keyword. + +2006-11-23 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-in-expression-p): Use `read' and `eq' to test + the first element of the list. Previuosly, the pattern (foo) + wrongly matched (foobar) because we used (looking-at <symbol>). + + * swank-cmucl.lisp (setf-definitions): Also include defs which + were created with (defun (setf NAME) ...). Previously we only + found definitions created with defsetf or define-setf-expander. + 2006-11-22 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-edit-definition): Don't hide error messages.

1 0

[slime-devel] Small fixes
by Antonio Menezes Leitao 23 Nov '06

23 Nov '06

Hi, I would like to propose an small improvement to slime-edit-definition so that it correctly identifies setf forms (which it doesn't, at the moment). The change is limited to the interactive pseudo-call. Instead of (defun slime-edit-definition (name &optional where) "Lookup the definition of the name at point. If there's no name at point, or a prefix argument is given, then the function name is prompted." (interactive (list (slime-read-symbol-name "Name: "))) ...) use (defun slime-edit-definition (name &optional where) "Lookup the definition of the name at point. If there's no name at point, or a prefix argument is given, then the function name is prompted." (interactive (list (slime-edit-definition-query (slime-extract-context)))) ...) The function slime-edit-definition-query is just a stripped down version of slime-trace-query: (defun slime-edit-definition-query (spec) "Ask the user which function to edit; SPEC is the default. The result is a string." (cond ((null spec) (slime-read-from-minibuffer "Name: ")) ((symbolp spec) (symbol-name spec)) (t (destructure-case spec ((setf n) (prin1-to-string spec)) (((:defun :defmacro :defgeneric) n) (prin1-to-string n)) ((:defmethod n &rest _) (prin1-to-string n)) ((:call caller callee) (prin1-to-string callee)) (((:labels :flet) &rest _) (slime-read-from-minibuffer "Name: ")))))) That would be enough, if it were not for the fact that, in some cases, Slime is not correctly identifying the relevant context information. One reason seems to be the slime-in-expression-p function. Here are a few examples (the . is the cursor): (defun zdzz () (setfabble-p fo.o)) -> (:defun (setf foo)) (defun zdzz () (setfab.ble-p foo)) -> (:defun (setf setfabble-p)) (defmacro-transform bla () (bo.o)) -> (:call (:defmacro bla) boo) (defmacro-transform b.la () (boo)) -> (:defmacro bla) (defmacro-tran.sform bla () (boo)) -> (:defmacro defmacro-transform) (defunia (bsd.o)) -> (:call (:defun (bsdo)) bsdo) (defun.ia (bsdo)) -> (:defun defunia) One problem is the (looking-at (symbol-name p)) form in slime-in-expression-p that, obviously, is happy even if the symbol being searched only _partially_ matches the actual text. So either we replace it with something similar to (looking-at (concat (symbol-name p) "\\S_")) or, in order to deal with end-of-buffer limits, with something similar to (let ((symbol (buffer-substring-no-properties (point) (save-excursion (forward-sexp 1) (point))))) (string= symbol (symbol-name p))) With this change, the examples now produce: (defun zdzz () (setfabble-p fo.o)) -> foo (defun zdzz () (setfab.ble-p foo)) -> (:call (:defun zdzz) setfabble-p) (defmacro-transform bla () (bo.o)) -> (:call bla boo) (defmacro-transform b.la () (boo)) -> bla (defmacro-tran.sform bla () (boo)) -> (:call bla defmacro-transform) (defunia (bsd.o)) -> (:call (bsdo) bsdo) (defun.ia (bsdo)) -> (:call (bsdo) defunia) It's better but there are still some problems, visible in the last three examples. Fortunately, they don't severely affect what I want to do and, besides, I'm not sure about the inner workings of the slime-in-expression-p function (it seems incomplete, imho), so I'll leave it that way for now. BTW, this was only superficially tested, but it seems to work. Best regards, António Leitão.

4 8

[slime-devel] Parsing the in-package form
by Antonio Menezes Leitao 23 Nov '06

23 Nov '06

Hi, If I'm not mistaken, the current Slime version doesn't correctly parse in-package forms when the package name is a string or a keyword. This can be easily seen by writing in an edit buffer (in-package :foo) or (in-package "FOO") and then pressing C-c M-p (slime-repl-set-package) The following replacement correct this behaviour. (defun slime-search-buffer-package () (save-excursion (when (let ((case-fold-search t) (regexp "^(\\(cl:\\|common-lisp:\\)?in-package\\>[ \n\t\r':\"]*")) (or (re-search-backward regexp nil t) (re-search-forward regexp nil t))) (goto-char (match-end 0)) (let ((start (point))) (let ((pkg (ignore-errors (read (current-buffer))))) (and pkg (format "%S" pkg))))))) Best regards, António Leitão.

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 22 Nov '06

22 Nov '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1004 slime/ChangeLog:1.1005 --- slime/ChangeLog:1.1004 Tue Nov 21 17:00:22 2006 +++ slime/ChangeLog Wed Nov 22 10:29:23 2006 @@ -1,3 +1,7 @@ +2006-11-22 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-edit-definition): Don't hide error messages. + 2006-11-21 Helmut Eller <heller(a)common-lisp.net> * swank.lisp (*coding-system*): "Coding systems" are now strings

1 0

[slime-devel] compiling forms/regions/defuns with (optimize (debug 3) (speed 0) (safety 0))
by Marco Baringer 22 Nov '06

22 Nov '06

what do people think about a varient of slime-compile-defun which wrapped the code in (locally (declaim (optimize (speed 0) (safety 3) (debug 3))) ,@form) i'd bind this to C-u C-c C-c (and C-u C-c C-k) good idea? bad idea? -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

8 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel