slime-devel February 2004

slime-devel@common-lisp.net

24 participants
50 discussions

[slime-devel] Interactive compile loses DSPEC info
by Alain.Picard＠memetrics.com 03 Mar '04

03 Mar '04

Another one: I'm using latest CVS slime + Lispworks on Linux. If I compile and load my system from scratch, I can use M-. to jump around function definitions. but if I go to a function, hit C-c C-c to recompile the function, jump to a different emacs buffer and try M-. on the newly compiled function, I now get: make-single-line (:error The file #P"/tmp/filecLlfIH.lisp" does not exist.) (:location (:file /home/kooks/XOS/Bullseye/src/Common/generic-utilities.lisp) (:function-name MAKE-SINGLE-LINE)) in the *XREF buffer. Cheers,

3 7

[slime-devel] thread manipulation
by Marco Baringer 29 Feb '04

29 Feb '04

i've just commited a patch which allows you to do "stuff" with the threads in slime-list-threads. Killing threads: (bound to k in the slime-list-thread menu), simply kill-thread the thread at point. (Only implemented on OpenMCL). Attaching a slime-repl to a thread: (bound to a in the slime-list-thread menu) This will interuppt the thread, start a (fore ground) server in it and attach to that server in a new repl buffer. Debugging a thread: (bound to d in the slime-list-thread menu) This will interuppt the thread and then immediatly signal a simple-error putting you in an sldb-buffer. The backtrace will contain a bunch of extra frames intreduced by the simple-error, but all the restarts and frames are there. This has only been tested on OpenMCL and has, more than once, rendered my original (started via terminal) lisp unusable. -- 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

2 7

[slime-devel] What does "pipelined request" mean?
by Peter Seibel 29 Feb '04

29 Feb '04

I've got a busted connection to CLISP (along with several other connections to other Lisps which seem to be working) Whenever I type anything in the CLISP REPL I get a message from emacs of the form: ; pipelined request... (swank:listener-eval " ") What does this mean? -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

2 3

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 29 Feb '04

29 Feb '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.272 slime/ChangeLog:1.273 --- slime/ChangeLog:1.272 Fri Feb 27 07:32:06 2004 +++ slime/ChangeLog Sat Feb 28 04:13:26 2004 @@ -1,3 +1,21 @@ +2004-02-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-compilation-finished-hook): New hook variable. + (slime-compilation-finished): Call it. + (slime-maybe-show-xrefs-for-notes): New function. + (slime-make-default-connection): Use the current connection. + (slime-connection-at-point): New function. + (slime-goto-connection, slime-connection-list-make-default): Use + it. + (slime-draw-connection-list): Minor cleanups. + + Define selectors for t and c for thread and connection list. + + * swank.lisp: (*initial-pprint-dispatch-table*) + (*arglist-pprint-dispatch-table*): Workaround for bug in + CLISP. Don't supply nil as argument to copy-pprint-dispatch. + (print-cons-argument): Insert a space after the car. + 2004-02-27 Marco Baringer <mb(a)bese.it> * slime.el (slime-read-port-and-connect,

1 0

[slime-devel] Re: Compiler Notes -- some suggestions
by Helmut Eller 28 Feb '04

28 Feb '04

Jan Rychter <jan(a)rychter.com> writes: > >>>>> "Helmut" == Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > Helmut> Jan Rychter <jan(a)rychter.com> writes: > >> But perhaps I'm missing something? > > Helmut> The primary reason for this browser is that some warnings don't > Helmut> have a source location, i.e., they don't belong to a particular > Helmut> source form but to the entire file or compilation unit. The > Helmut> other reason is that SBCL produces about hundred redefinition > Helmut> style warnings when I recompile swank-sbcl.lisp and I found it > Helmut> difficult to find the few (non-style) warnings. > > Hmm, I think I understand now. Thanks. > > >> All in all, I'd suggest making this buffer pop up optionally, I'll > >> just disable that option then, I guess. And it would be vastly more > >> useful if the keys were electric and the active extents began at the > >> beginning of the line (or if the electric keys jumped to the > >> appropriate place in the buffer). > > Helmut> OK. I'll remove this feature and only use it in my private > Helmut> setup. > > If people find it useful, perhaps it's a good candidate for a defcustom? Will make it customizable, disabled by default. > I just wanted to ask, because I intend to do some usability work on > slime (making sure that windows open and close properly, that > keybindings are consistent, etc) -- I've been wondering whether I > understand how this feature is supposed to work and whether I should try > to fix things in it. Yeah, some things could be improved. Helmut.

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 28 Feb '04

28 Feb '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.271 slime/ChangeLog:1.272 --- slime/ChangeLog:1.271 Thu Feb 26 17:31:13 2004 +++ slime/ChangeLog Fri Feb 27 07:32:06 2004 @@ -1,3 +1,25 @@ +2004-02-27 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-read-port-and-connect, + slime-read-port-and-connect-to-running-swank): Refactor + slime-read-port-and-connect into two functions so that + slime-thread-attach can use the logic in + slime-read-port-and-connect. + (slime-thread-control-mode-map): Added key bindings for + slime-thread-kill, slime-thread-attach, slime-thread-debug and + slime-list-threads. + (slime-thread-kill, slime-thread-attach, slime-thread-debug): New + functions. + + * swank-backend.lisp (kill-thread): Added to swank interface. + + * swank-openmcl.lisp (kill-thread): Implement. + + * swank.lisp (start-server): Add optional background argument, + defaults to *swank-background*. + (lookup-thread-by-id): New function. + (debug-thread): New function. + 2004-02-26 Peter Seibel <peter(a)javamonkey.com> * slime.el (slime-draw-connection-list): Use text-properties to

1 0

[slime-devel] CLISP breakage
by Peter Seibel 27 Feb '04

27 Feb '04

So I just noticed that due to a bug in CLISP's implementation of COPY-PPRINT-DISPATCH swank.lisp won't load. I sent a bug report to clisp-devel; in the meantime here's a patch that will get CLISP users back on their feet, though depending on how you read the spec, this may or may not really be equivalent. (I assume this use of copy-pprint-dispatch went in recently since I was having no problems with CLISP until today.) -Peter Index: swank.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank.lisp,v retrieving revision 1.127 diff -u -r1.127 swank.lisp --- swank.lisp 26 Feb 2004 07:13:01 -0000 1.127 +++ swank.lisp 27 Feb 2004 20:31:12 -0000 @@ -697,7 +697,7 @@ ;;; cover cases like (&key (function #'cons) (quote 'quote)). Too ;;; much code for such a minor feature? -(defvar *initial-pprint-dispatch-table* (copy-pprint-dispatch nil)) +(defvar *initial-pprint-dispatch-table* (copy-pprint-dispatch)) (defun print-cons-argument (stream object) (pprint-logical-block (stream object :prefix "(" :suffix ")") @@ -710,7 +710,7 @@ (princ object stream))) (defvar *arglist-pprint-dispatch-table* - (let ((table (copy-pprint-dispatch nil))) + (let ((table (copy-pprint-dispatch))) (set-pprint-dispatch 'cons #'print-cons-argument 0 table) (set-pprint-dispatch 'symbol #'print-symbol-argument 0 table) table)) -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

1 0

[slime-devel] Compiler Notes -- some suggestions
by Jan Rychter 27 Feb '04

27 Feb '04

I've been thinking about the Compiler Notes buffer that pops up after compilation. I have to admit I don't find it particularly useful as it is now, for a number of reasons: -- it shows very little information by default: -+ All (21) |[+] Notes (8) `[+] Warnings (13) -- it obscures my REPL, -- I have to do "C-x o C-x k" to kill it (or at least "C-x o q"), which I consider to be a major usability flaw, -- in the buffer, keys are not electric, and the usual "n" or "p" don't get me anywhere, -- the active extents where pressing RET would take me to the code do not begin at the beginning of the line, so even if I do C-n several times, I still have to C-f to the appropriate part of the tree where I can press RET, -- overall, there seems to be no information in the tree that I wouldn't normally get by just pressing M-n or M-p to navigate the compiler notes. But perhaps I'm missing something? I toyed with the idea of making this buffer more useful by adding electric "n" and "p" commands, which would also adjust the source buffer. That would be similar to how M-n and M-p keys work in the source buffer. But then I discovered that the data structure used is a tree, so jumping across leafs isn't all that easy. And I can't really understand why it is a tree? Only to provide the "All", "Warnings", and "Notes" branches, or for some other reason? Do we have nested warnings? All in all, I'd suggest making this buffer pop up optionally, I'll just disable that option then, I guess. And it would be vastly more useful if the keys were electric and the active extents began at the beginning of the line (or if the electric keys jumped to the appropriate place in the buffer). --J.

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 27 Feb '04

27 Feb '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.264 slime/ChangeLog:1.268 --- slime/ChangeLog:1.264 Wed Feb 25 02:29:59 2004 +++ slime/ChangeLog Thu Feb 26 02:19:07 2004 @@ -1,3 +1,40 @@ +2004-02-26 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-backend.lisp (:swank): export connection-info. + + * swank-allegro.lisp (lisp-implementation-type-name): Implement + it. + + * swank-sbcl.lisp (compile-file-for-emacs): Load the fasl file + regardless of f-p. + + * swank.lisp (swank-pprint): Bind *package* to *buffer-package*. + Reported by Alan Picard. + + * swank-lispworks.lisp (dspec-buffer-position): Renamed from + dspec-buffer-buffer-position. Handle dspecs of the form (defmacro + foo). Reported by Alan Picard. + (arglist-string): Handle unknown arglists properly. + +2004-02-25 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-cmucl.lisp (arglist-string): Delay the call to + di::function-debug-function until it is actually needed. + (compile-file-for-emacs): Load the fasl file irrespective of + COMILE-FILE's third return value. + + * swank.lisp (connection-info): New function. + (open-streams): Don't send the :check-protocol-version message. Now + handled with CONNECTION-INFO. + + * slime.el (slime-symbol-at-point): Don't skip backwards across + whitespace when we are at the first character of a symbol. To + handle this case: skip symbol constituents forward before skipping + whitespace backwards. Reported by Jan Richter. + (slime-connection-close-hook, slime-next-connection) + (slime-make-default-connection): Remove extra call to format. + (slime-init-connection-state): Use only a single RPC instead of 4. + 2004-02-25 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-with-chosen-connection): Bind @@ -5,8 +42,10 @@ slime-buffer-connection is a buffer local variable not a dynamic variable. (slime-find-connection-by-type-name) - (slime-read-lisp-implementation-type-name): Where lost during the + (slime-read-lisp-implementation-type-name): Were lost during the merge. + (sldb-fetch-more-frames): Use (goto-char (point-max)) instead of + end-of-buffer. 2004-02-25 Peter Seibel <peter(a)javamonkey.com>

3 2

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 27 Feb '04

27 Feb '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.268 slime/ChangeLog:1.271 --- slime/ChangeLog:1.268 Thu Feb 26 02:19:07 2004 +++ slime/ChangeLog Thu Feb 26 17:31:13 2004 @@ -1,3 +1,21 @@ +2004-02-26 Peter Seibel <peter(a)javamonkey.com> + + * slime.el (slime-draw-connection-list): Use text-properties to + associate the connections each line of the connections list + buffer. + +2004-02-26 Peter Seibel <peter(a)javamonkey.com> + + * slime.el (slime-list-connections): Make the buffer created by + this function do a bit more: Can use it to switch to different + connections and change the default. + +2004-02-26 Marco Baringer <mb(a)bese.it> + + * swank-openmcl.lisp (ccl::force-break-in-listener): Pass a + condition object to invoke-debugger. + Patch by Bryan O'Connor <bryan-slime(a)lunch.org> + 2004-02-26 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * swank-backend.lisp (:swank): export connection-info.

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 February 2004