slime-devel May 2006

slime-devel@common-lisp.net

37 participants
41 discussions

[slime-devel] slime apparently mis-reporting closed connection
by Samium Gromoff 26 Oct '07

26 Oct '07

After well into the second decade of slime-disconnect/slime-connect loop iteration (interweaved with normal operation) the emacs side of slime stopped recognising connection status. I`m doing a slime-disconnect, restarting swank and slime-connect, however immediately after this either a slime-load-file or a (load ...) in slime repl result in a message "Connection closed." i have some time before i will have to reboot the machine, and until then i can provide various forensics upon request... regards, Samium Gromoff

5 5

[slime-devel] slime-apropos-package now sorts correctly
by Hoehle, Joerg-Cyril 20 Apr '07

20 Apr '07

Hi, slime-apropos-package now conforms to its specification and also sorts symbols printed with package prefix. I supply the patches as attachments in the hope that MS-Windows nor MS-Outlook will break the TAB and LF characters of the original diff. I hope this is fine. Regards, Jörg Höhle.

3 3

[slime-devel] slime-display-edit-hilights
by Marco Baringer 23 Dec '06

23 Dec '06

for those of you who don't follow c.l.l (which is probaly a good idea) i commited William Bland's patch[1]. see the ChangeLog for details. 1 - http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/e1d0b7bf… -- -Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

8 20

[slime-devel] How to inspect locals
by Jonathon McKitrick 27 Aug '06

27 Aug '06

Hi all, when running SBCL and a condition occurs that causes a break, how can I view the locals that have been bound in the function? Viewing the arguments isn't hard, but I cannot seem to figure out the locals. -Jonathon -- "I am sure that Jesus would use a command prompt. Hello? Ten Commandments??"

12 17

[slime-devel] swank reloading problem
by Cyrus Harmon 19 Jun '06

19 Jun '06

I'm trying to debug getting threads running on SBCL/x86/MacOS and in doing so I've come across a strange problem where something (presumably clim-desktop.asd) is requiring swank, which is causing swank.asd to get reloaded and swank-backend is getting recompiled, which causes current-thread to get redefined to 0. This seems to wreak havoc with some of the locking stuff, which presumably has various locks held while it's trying to output the results of the compilation. Should the definterface stuff in swank-backend have some sort of check to see if these haven't been previously implemented before overwriting the previous method definitions? Thanks, Cyrus

4 4

[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] Slime/CMU hangs on GC
by Florian Ebeling 05 Jun '06

05 Jun '06

My emacs in slime mode hangs quite oft imidiatly after announcing a GC run, usually from a Slime mode buffer, not from REPL. I use CMUCL and Slime from CVS. Is this a known behaviour? Florian -- Florian Ebeling florian.ebeling(a)gmail.com

4 3

[slime-devel] On the numbering of restarts in SLDB
by Gary King 31 May '06

31 May '06

Although it makes perfect sense, I find it irritating that the number for the [abort-request] restart in SLDB depends on how many other restarts are active. For clarity's sake, here is a list of restarts: > Restarts: > 0: [RETRY] Retry performing #<LOAD-OP NIL #x84F81F6> on #<SYSTEM > "cl-containers" #x84E8EE6>. > 1: [ACCEPT] Continue, treating #<LOAD-OP NIL #x84F81F6> on > #<SYSTEM "cl-containers" #x84E8EE6> as having been successful. > 2: [ABORT-REQUEST] Abort handling SLIME request. > 3: [ABORT-BREAK] Reset this process > 4: [ABORT] Kill this process In this case, I should type '2' to give up on this request and try something else. In other cases, however, I might need to type '7' or '5' or whatever. This means that I have to look and see what to type every single time I hit an error (and, hey, I hit a lot of errors in my code!). It also scares me that I could misread and type the key for [abort-break] or [abort] by accident. Here is my suggestion as to what the list of restarts might look like: > Restarts: > 4: [RETRY] Retry performing #<LOAD-OP NIL #x84F81F6> on #<SYSTEM > "cl-containers" #x84E8EE6>. > 3: [ACCEPT] Continue, treating #<LOAD-OP NIL #x84F81F6> on > #<SYSTEM "cl-containers" #x84E8EE6> as having been successful. > 2: [ABORT-REQUEST] Abort handling SLIME request. > 1: [ABORT-BREAK] Reset this process > 0: [ABORT] Kill this process or > Restarts: > 0: [RETRY] Retry performing #<LOAD-OP NIL #x84F81F6> on #<SYSTEM > "cl-containers" #x84E8EE6>. > 1: [ACCEPT] Continue, treating #<LOAD-OP NIL #x84F81F6> on > #<SYSTEM "cl-containers" #x84E8EE6> as having been successful. > A: [ABORT-REQUEST] Abort handling SLIME request. > R: [ABORT-BREAK] Reset this process > K: [ABORT] Kill this process In both cases, the three 'always there' restarts will always have the same keyboard binding. In the later example, they are non-numeric. I'm willing to figure out how to implement this _if_ the general opinion is that this is a good idea. What is the general opinion? thanks, -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

8 9

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

30 May '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.901 slime/ChangeLog:1.903 --- slime/ChangeLog:1.901 Sat May 27 05:06:12 2006 +++ slime/ChangeLog Mon May 29 19:41:00 2006 @@ -1,3 +1,30 @@ +2006-05-30 Tobias Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-get-temp-buffer-create): New keyword REUSEP + which indicates whether an already-existing buffer named like the + buffer to be created should be reused, i.e. not killed, then + freshly created. Update docstring accordingly. + (slime-with-output-to-temp-buffer): Make &optional arg MODE an + &key keyword arg. Add REUSEP keyword. + (slime-macroexpansion-minor-mode-map): Make remapped `undo' update + highlighted edits in the macroexpansion buffer. + (slime-eval-macroexpand-in-place): Update highlighted edits when + macroexpanding in-place. + (slime-eval-macroexpand): Reuse macroexpansion buffer if it exists + already to preserve `undo' functionality. + +2006-05-30 Tobias Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-use-autodoc-mode): Fix typo in docstring. + (slime-use-highlight-edits-mode): New variable, analogous to + SLIME-USE-AUTODOC-MODE. + (slime-setup, slime-lisp-mode-hook): Make above variable + work. Also, activates the HIGHLIGHT-EDITS-MODE in proper way (thus + avoiding the nasty "Toggling ... off; better pass an explicit + argument." message.) + + * slime.el: Fix typo in comment about communication protocol. + 2006-05-27 Alan Ruttenberg <alanr-l(a)mumble.net> * swank-abcl: slot-boundp-using-class slot-value-using-class so you can inspect instances

1 0

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

28 May '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.900 slime/ChangeLog:1.901 --- slime/ChangeLog:1.900 Sat May 27 00:18:13 2006 +++ slime/ChangeLog Sat May 27 05:06:12 2006 @@ -11,7 +11,7 @@ Also make expanding of expressions work that are quoted like, for instance, "'(FOO BAR)" if point is placed at the opening paren. -006-05-24 Brian Downing <bdowning(a)lavos.net> +2006-05-24 Brian Downing <bdowning(a)lavos.net> * swank.lisp (recursively-compute-most-completions & friends): Micro-optimize the fuzzy completion engine, improving performace

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 May 2006