slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 24 Nov '03

24 Nov '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.104 slime/ChangeLog:1.109 --- slime/ChangeLog:1.104 Sun Nov 23 02:15:57 2003 +++ slime/ChangeLog Sun Nov 23 22:24:36 2003 @@ -1,4 +1,47 @@ +2003-11-24 Luke Gorrie <luke(a)bluetail.com> + + * swank.lisp (eval-string-in-frame): Fixed symbol-visibility + problem (thanks Lawrence Mitchell). + + * swank-sbcl.lisp (function-source-location): Use TRUENAME to + resolve source file name (thanks Lawrence Mitchell). + + * slime.el (slime-goto-source-location): Fixes when finding + definition by regexp: open the right file (was missed), and + tweaked regexp to match more 'def' forms - especially + `defmacro-mundanely' (hyphen wasn't allowed before). + 2003-11-23 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (sldb-fetch-more-frames): Call swank:backtrace instead + of (renamed) swank:backtrace-for-emacs. + + * swank-cmucl.lisp, swank-sbcl.lisp, swank-openmcl-lisp: Updated + to use new debugger interfaces in swank-backend.lisp. + + * swank-backend.lisp (backtrace, eval-in-frame, frame-catch-tags, + frame-locals, frame-source-location-for-emacs): More interface + functions. + + * slime.el (slime-goto-source-location): Added optional `align-p' + argument for :file and :emacs-buffer location types. This is for + OpenMCL - unlike CMUCL its positions are not character-accurate so + it needs to be aligned to the beginning of the sexp. + (slime-connect): Don't delete a random window when *inferior-lisp* + isn't visible. + + * swank-cmucl.lisp: Tidied up outline-minor-mode structure and + added comments and docstrings. + + * swank-cmucl.lisp, swank-sbcl.lisp, swank-openmcl-lisp: Updated + to use new debugger interface in swank-backend.lisp. + + * swank-backend.lisp (call-with-debugging-environment, + sldb-condition, debugger-info-for-emacs): More callbacks defined. + + * swank.lisp: Tidied up outline-minor-mode structure, added + comments and docstrings. + (sldb-loop): Took over the main debugger loop. * swank-openmcl.lisp: Updated after refactoring of other backends (was broken).

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 23 Nov '03

23 Nov '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.102 slime/ChangeLog:1.104 --- slime/ChangeLog:1.102 Sat Nov 22 02:45:24 2003 +++ slime/ChangeLog Sun Nov 23 02:15:57 2003 @@ -1,3 +1,23 @@ +2003-11-23 Luke Gorrie <luke(a)bluetail.com> + + * swank-openmcl.lisp: Updated after refactoring of other backends + (was broken). + + * slime.el (slime-goto-source-location): Align at beginning of + sexp after (:file name pos) and (:emacs-buffer buffer pos). + + * swank-sbcl.lisp (describe-symbol-for-emacs): Don't ask for + (documentation SYM 'class), CLHS says there isn't any 'class + documentation (and SBCL warns). + + * swank.lisp, swank-cmucl.lisp, swank-sbcl.lisp: Refactored + interface through swank-backend.lisp for: swank-compile-file, + swank-compile-string, describe-symbol-for-emacs (apropos), + macroexpand-all, arglist-string. + + * swank-backend.lisp: New file defining the interface between + swank.lisp and the swank-*.lisp implementation files. + 2003-11-22 Brian Mastenbrook <bmastenb(a)cs.indiana.edu> * swank.asd: ASDF definition to load "swank-loader.lisp". This is

1 0

[slime-devel] Refactoring, take two
by Luke Gorrie 23 Nov '03

23 Nov '03

Ahoy, I'm having another crack at backend refactoring. This time I'm going "by the book" and doing it incrementally on CVS HEAD. The plan is to move to James's plan [1], roughly: swank.lisp: shared, portable code swank-backend.lisp: defines the interface to non-portable code swank-{cmucl,...}.lisp: implements the interface from swank-backend.lisp Ultimately each file will be a different package, but for now all files are in the SWANK package. The advantage is that nothing breaks by default - some things are now working via swank-backend.lisp, but the rest (not refactored yet) is just like before and still works. The most significant refactoring so far is the compiler-note reportage: now each backend detects a compiler note in whatever non-portable way is appropriate, then resignals it as a `swank:compiler-condition' which is handled in swank.lisp. So all the notes-database business is shared now. I also switched to using generic functions to define callbacks and methods to implement them. This seems like a neat fit compared with my ugly macro hacks from last time. Still hacking, so things may be a little unstable. Currently NB: I updated the FAIRLY-STABLE tag incase I'm breaking things. Currently HEAD should be okay on all platforms AFAIK. NB2: SLIME's surprisingly nice for doing major surgery on itself, at least when not breaking the debugger and repl :-) NB3: Thanks James, Dan, and Brian for helping me with OpenMCL access! Cheers, Luke 1: http://jamesjb.com/slime/slime-impl.txt

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 22 Nov '03

22 Nov '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.100 slime/ChangeLog:1.102 --- slime/ChangeLog:1.100 Wed Nov 19 08:14:17 2003 +++ slime/ChangeLog Sat Nov 22 02:45:24 2003 @@ -1,3 +1,24 @@ +2003-11-22 Brian Mastenbrook <bmastenb(a)cs.indiana.edu> + + * swank.asd: ASDF definition to load "swank-loader.lisp". This is + useful for starting the Swank server in a separate Lisp and later + connecting with Emacs. The file includes commentary. + +2003-11-22 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-connect): Slightly reordered some window + operations to ensure that *slime-repl* is popped up after `M-x + slime-connect'. + (slime-show-last-output): If the *slime-repl* buffer is already + visible in any frame, don't change anything. + + * swank.lisp (listener-eval): Format results in *buffer-package*. + Exporting (CREATE-SWANK-SERVER <port>). This function can be + called directly to start a swank server, which you can then + connect to with `M-x slime-connect'. It takes a port number as + argument, but this can be zero to use a random available port. + The function always returns the actual port number being used. + 2003-11-19 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * swank.lisp: Better printing off return values. In the REPL

2 1

[slime-devel] Slime feature requests
by Brian Mastenbrook 22 Nov '03

22 Nov '03

Hello fellow hackers, I've been using slime for some time now, and I /really/ like it. It feels much more integrated than ilisp, and has several nice advantages. I like the ability to run my lisp independently of emacs - that way when emacs goes down (I'm using emacs CVS, and it does happen from time to time) my session isn't lost, and I can also logout/login without disrupting my lisp session. It seems that a few weeks back, SLIME switched to using a file to communicate the port that swank would be listening on, and swank:start-server started taking this as a required argument. Can I request that swank:start-server go back to not requiring an argument and starting the server on the default port - and possibly allow the choice of another port somehow? It might also be nice to include a simple swank .asd file like the one I've attached to make it easier to start the swank server in a fresh lisp. I've also noticed that SLIME seems to like to pop up the REPL in the current frame when sending definitions via C-M-x, and resize it if it's already active. I like keeping the REPL in another window, and would request that SLIME not touch or rearrange anything unless the slime repl is not visible. Lastly, it seems that slime prints its results from the CL-USER package, regarldess of the user's current package in the REPL. Since it obviously knows the current package well enough to include it in the REPL prompt, would it be possible to make it print output from that package? Thanks! -- Brian Mastenbrook bmastenb(a)cs.indiana.edu http://cs.indiana.edu/~bmastenb/

2 1

[slime-devel] CVS update:
by Luke Gorrie 22 Nov '03

22 Nov '03

Update of /project/slime/cvsroot/CVSROOT In directory common-lisp.net:/tmp/cvs-serv10039 Modified Files: loginfo Log Message: Revert the switch over to my script - it was losing the diffs. Will use danb's nice idea of mailing ChangeLog diffs to slime-devel from crontab. Date: Fri Nov 21 23:29:42 2003 Author: lgorrie

1 0

[slime-devel] CVS update:
by Helmut Eller 19 Nov '03

19 Nov '03

Update of /project/slime/cvsroot/slime In directory common-lisp.net:/tmp/cvs-serv5952 Modified Files: ChangeLog Log Message: *** empty log message *** Date: Wed Nov 19 08:14:18 2003 Author: heller

1 0

[slime-devel] CVS update:
by Helmut Eller 19 Nov '03

19 Nov '03

Update of /project/slime/cvsroot/slime In directory common-lisp.net:/tmp/cvs-serv31757 Modified Files: ChangeLog Log Message: *** empty log message *** Date: Wed Nov 19 07:59:15 2003 Author: heller

1 0

[slime-devel] Slime values display and debug display
by Raymond Toy 18 Nov '03

18 Nov '03

I've noticed that when a function returns multiple values, slime concats them together and displays them on one line, separated by commas. This works fine, until you get vector or other large object. Then the display is not so good: 0.3314521116706366d0, 3.6798576593736937d-15, 42, 0, #(((0.0d0 0.7853981633974483d0) 0.30842513753404244d0 3.4242068906347456d-15) ((0.7853981633974483d0 1.0d0) 0.023026974136594155d0 2.5565076873894826d-16)), #(1 2 0 ...) Is there some way to control this? I do not mind the CMUCL way of displaying each value on a separate line. Also, in sldb, is there a way to get the backtrace to pprint the args? I've become accustomed to the way CMUCL displays it, so I find it hard to see the args anymore. Here is what sldb produces: 0: (DQAWO 15 #<Interpreted Function (LAMBDA (X) (LET # #)) {41B50251}> 0.0d0 5.0d0 2.0d0 0.0d0 1.0d-8 0.0d0 0.0d0 0 0 200 800 0 #(0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ...) #(0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 ...) NIL NIL)[:EXTERNAL] Here is what happens in *inferior-lisp*: (DQAWO 15 #<Interpreted Function (LAMBDA # #) {41423F11}> 0.0d0 5.0d0 2.0d0 0.0d0 1.0d-8 0.0d0 0.0d0 0 0 200 800 0 #(0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ...) #(0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 0.0d0 ...) NIL NIL)[:EXTERNAL] I find the latter FAR easier to read. Anyway, I've finally switched over from ilisp because slime can do what I want and only has minor issues like the above. Keep up the good work! Ray

1 0

[slime-devel] other-window functions
by Christian Lynbech 18 Nov '03

18 Nov '03

One thing that I miss in slime is "other-window" versions of functions such as `slime-edit-fdefinition'. ------------------------+----------------------------------------------------- Christian Lynbech | christian #\@ defun #\. dk ------------------------+----------------------------------------------------- Hit the philistines three times over the head with the Elisp reference manual. - petonic(a)hal.com (Michael A. Petonic)

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel