slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Fuzzy completion
by Levente Mészáros 16 Jun '06

16 Jun '06

Hi, Although I'm not a big emacs guru, so things might be implemented simpler, but I did what I could with a resonable effort. Still you may or may not find this useful. This is not a final patch for two reasons: first I'm not even sure it's worth it and if nobody is interested I will just keep it in my local repo. Second, it breaks current functionality: the one which continuously replaces text in the target buffer while you move up and down in the completion window with the current completion (selection). Personally I found that superfluous. So this is a somewhat different end user experience for fuzzy completion. It is a little bit closer to the other non fuzzy completion in that it does not take the focus away from the buffer you are editing and there are some other minor differences. I introduced a new minor mode called slime-fuzzy-target-buffer-completions-mode for the target buffer during fuzzy completion. You may find it usefull to bind your paredit open and close keys to (the ones bound to insert-parentheses and move-past-close-and-reindent) slime-fuzzy-select-and-process-event-in-target-buffer in the keymaps called slime-target-buffer-fuzzy-completions-map and slime-fuzzy-completions-map. Here is how it works (- means not yet implemented): When focus is in the target window (replace tab with your favorite key binding): + tab shows completion window if it was not open + tab updates completion window if there was editing since last time tab was pressed + tab implicitly completes if there's only one match + tab selects current completion if there were no editing since last tab (double tab) even if there are multiple matches + tab closes completion window if there are no matches at all - tab distinguishes between function and other symbols and puts an extra space before caret if mandatory parameters exists - tab puts the caret after the list in the target for unary function symbols + left/right moves caret in target window + up/down moves caret in completion window even though the focus is in the target window (changes current completion) + space/enter/(/) implicitly selects current completion and processes event in target window (paredit takes care about the rest) + normal editing operations allowed in target window - editing implicitly updates completion window in the background during editing (by a timer) + C-q closes completion window When focus is in the completion window: + cursor keys navigate + tab/mouse2 selects current completion and closes completion window + space/enter/(/) selects current completion, closes completion window and processes event in the target window + q closes completion window Cheers, levy -- There's no perfectoin

5 4

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

14 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.906 slime/ChangeLog:1.907 --- slime/ChangeLog:1.906 Sun Jun 11 07:02:08 2006 +++ slime/ChangeLog Wed Jun 14 10:58:37 2006 @@ -1,3 +1,9 @@ +2006-06-14 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * slime.el (slime-goto-definition): If all definitions of a name + have the same location, go there directly rather than presenting + an xref buffer. + 2006-06-11 Douglas Crosher <dcrosher(a)common-lisp.net> * swank-scl (ext:stream-write-chars): update for SCL 1.3.

1 0

[slime-devel] Attempt to fix semantic indentation with clisp
by Damyan Pepper 14 Jun '06

14 Jun '06

This patch attempts to fix semantic indentation with clisp. I'm not sure how great an idea it is, but it seems to work for me. It works by changing the macro-functon on common-lisp:defmacro to one that also stores the arglist on the defined macro's symbol-plist. Strictly speaking, I don't believe you're meant to modify symbols in the common-lisp package in this way, but it seems to work with clisp. Any thoughts would be much appreciated! 2006-06-14 Damyan Pepper <damyanp(a)gmail.com> * swank-clisp.lisp: Replace common-lisp:defmacro with a modified version that stores the argument list in a way that can be retrieved with swank-backend:arglist. This makes semantic indentation work for macros with &body arguments. $ cvs -q diff -u Index: swank-clisp.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-clisp.lisp,v retrieving revision 1.58 diff -u -r1.58 swank-clisp.lisp --- swank-clisp.lisp 22 Mar 2006 16:40:01 -0000 1.58 +++ swank-clisp.lisp 14 Jun 2006 11:47:00 -0000 @@ -137,12 +137,13 @@ (defimplementation arglist (fname) (block nil - (or (ignore-errors - (let ((exp (function-lambda-expression fname))) - (and exp (return (second exp))))) - (ignore-errors - (return (ext:arglist fname))) - :not-available))) + (or (get fname 'arglist) + (ignore-errors + (let ((exp (function-lambda-expression fname))) + (and exp (return (second exp))))) + (ignore-errors + (return (ext:arglist fname))) + :not-available))) (defimplementation macroexpand-all (form) (ext:expand-form form)) @@ -580,6 +581,22 @@ #+lisp=cl (ext:quit) #-lisp=cl (lisp:quit)) +♀ + +;;; Replace cl:defmacro with our own that stores the arglists +(defvar *old-defmacro* (copy-symbol 'common-lisp:defmacro t)) + +(defmacro defmymacro (&environment env &whole whole name params &body body) + (declare (ignore body)) + `(progn + (setf (get ',name 'swank-backend::arglist) ',params) + ,(funcall (macro-function *old-defmacro*) whole env) + ',name)) + +(setf *old-defmacro* (copy-symbol 'common-lisp:defmacro t)) +(setf (macro-function 'common-lisp:defmacro) (macro-function 'defmymacro)) + + ;;; Local Variables: ;;; eval: (put 'compile-file-frobbing-notes 'lisp-indent-function 1) ;;; eval: (put 'dynamic-flet 'common-lisp-indent-function 1)

3 4

[slime-devel] Problems with swank connection
by Henda Carvalho 13 Jun '06

13 Jun '06

Hi there, I´m using slime and I'm having a problem with the swank connection: (save-current-buffer (slime-disconnect) (if (get-buffer "*inferior-lisp*") (kill-buffer "*inferior-lisp*")) (slime) (if (not (slime-connected-p)) <error, do something> )) The problem is that the function 'slime-connected-p' is returning 'nil', meaning that there isn't a swank connection... Can somebody tell me why? I'm using windows xp, my lisp implementation is Allegro CL (version 7), and my Emacs is GNU Emacs 21.3.1. Best regards, Henda

4 4

Re: [slime-devel] Unable to get SLIME working with sbcl-0.9.13
by rif 12 Jun '06

12 Jun '06

Ah, maybe I spoke too soon. Apparently, I need to set swank:*communication-style* to something other than :spawn. Is it known that :spawn doesn't work with sbcl? I somehow thought I'd been using :spawn with sbcl on my other (home) machine, but maybe I was confused. rif

4 3

[slime-devel] Unable to get SLIME working with sbcl-0.9.13
by rif 12 Jun '06

12 Jun '06

Does slime work with the newest SBCL? I've tried both the CVS snapshot and the 2.0 release. In both cases, it seems to build a bunch of stuff, then gives me a prompt and instantaneously crashes ("Lisp connection closed unexpectedly: exited abnormally with code 256"). The last WARNING printed in *inferior-lisp* (ignoring style warnings) is WARNING: These Swank interfaces are unimplemented: (ACTIVATE-STEPPING CALLS-WHO DISASSEMBLE-FRAME INSPECT-FOR-EMACS SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) What am I doing wrong? Do I need to back off to an earlier SBCL? rif

1 0

[slime-devel] seting default directory
by Nikola Skoric 12 Jun '06

12 Jun '06

Hi there, I can't find out how I can set default directory in which slime should run. I tried to add (set-default-directory "foobar") to site-init.lisp, but things don't go that way, it seems to me... -- sig

4 3

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

11 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.905 slime/ChangeLog:1.906 --- slime/ChangeLog:1.905 Fri Jun 9 23:27:03 2006 +++ slime/ChangeLog Sun Jun 11 07:02:08 2006 @@ -1,4 +1,9 @@ +2006-06-11 Douglas Crosher <dcrosher(a)common-lisp.net> + + * swank-scl (ext:stream-write-chars): update for SCL 1.3. + 2006-06-09 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-abcl: Update to cvs version of abcl and warnings errors when compiling in a buffer will now be properly caught by slime vs current behavior of always saying 0 errors 0 warnings and printing

1 0

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

09 Jun '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.904 slime/ChangeLog:1.905 --- slime/ChangeLog:1.904 Wed May 31 15:27:31 2006 +++ slime/ChangeLog Fri Jun 9 23:27:03 2006 @@ -1,3 +1,9 @@ +2006-06-09 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-abcl: Update to cvs version of abcl and warnings errors + when compiling in a buffer will now be properly caught by slime vs + current behavior of always saying 0 errors 0 warnings and printing + them in the repl instead + 2006-05-31 Nathan Bird <nathan(a)acceleration.net> * swank.lisp (*sldb-quit-restart*): New variable.

1 0

[slime-devel] How to determine the top caller in Slime's REPL
by Philippe-André Lorin 09 Jun '06

09 Jun '06

Hello everybody. I'm a Slime newbie, trying to develop an application that is intended to be run in Emacs + Slime to allow for interactive modifications. I posted this to comp.lang.lisp, but got few replies; it is probably more appropriate here. In Slime, I need to be able to determine dynamically whether the "top caller" of the currently executing code is some specifically marked expression, or just one of all the other expressions typed at the REPL which might be running in parallel. An example should make the idea clearer. (defun f () ; This function is just here to show that the (in-marked-expression)) ; test is not necessarily lexically enclosed ; in the marked expression. (mark-and-eval (do () (nil) ; Just an infinite loop, to make sure the ; expression will be running forever in parallel. (assert (f)))) ; Here, IN-MARKED-EXPRESSION must always return T. (f) ; Note that the preceding (DO ...) is still running. => NIL ; Here, IN-MARKED-EXPRESSION must always return NIL. I can write the marked expression with complete freedom (for instance, I can add wrappers around it or preprocess it), but all the other expressions typed after it at the REPL are not under my control. Among the ideas I've tested, the following one sounded the most promising, but it doesn't work. I don't understand why. (defun in-marked-expression () (not (null (find-restart 'restart-in-restart-case)))) ; Are we in the ; restart-case? (defun f () (in-marked-expression)) (restart-case (do () (nil) (assert (f))) (restart-in-restart-case () nil)) (f) => T ; :( I also tried using a special variable or processes, with no luck. Any ideas? PS: I'm using CMUL on Ubuntu.

1 0

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