- slime-devel - mailman3.common-lisp.net

[slime-devel] Daily ChangeLog diff
by Helmut Eller 15 Dec '09

15 Dec '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1935 slime/ChangeLog:1.1936 --- slime/ChangeLog:1.1935 Sat Dec 12 13:58:46 2009 +++ slime/ChangeLog Mon Dec 14 04:06:34 2009 @@ -1,3 +1,7 @@ +2009-12-14 Stas Boukarev <stassats(a)gmail.com> + + * doc/slime.texi (ASDF): Document new commands. + 2009-12-12 Matthias Koeppe <mkoeppe(a)math.ucdavis.edu> * doc/slime.texi (Presentations): Add an example that illustrates Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.301 slime/contrib/ChangeLog:1.303 --- slime/contrib/ChangeLog:1.301 Sat Dec 12 13:43:29 2009 +++ slime/contrib/ChangeLog Mon Dec 14 10:28:46 2009 @@ -1,3 +1,33 @@ +2009-12-14 Tobias C. Rittweiler <tcr(a)freebits.de> + + Take recursiveness of LABELS into account for displaying local + arglists. I.e. make the following work: + + (labels ((iseven (x) + ...) + (isodd (y) + (if (zerop y) + nil + (iseven <>))))) ; Point is here + ...) + + As we only have information to look backward, we cannot show + arglist for ISODD within ISEVEN, though. + + * swank-arglists.lisp (extract-local-op-arglists): Handle LABELS + specially. + (find-subform-with-arglists): Adapted accordingly. Plus: Small + refactoring, and fix comparasion of local ops to properly deal + with arglist dummies. + +2009-12-14 Stas Boukarev <stassats(a)gmail.com> + + * slime-asdf.el (slime-delete-system-fasls): New command with a + shortcut `delete-system-fasls'. + + * swank-asdf.lisp (delete-system-fasls): New function. + (asdf-module-output-files): New function for finding fasls. + 2009-12-12 Matthias Koeppe <mkoeppe(a)math.ucdavis.edu> * slime-presentations.el (slime-reify-old-output): Revert change

1 0

[slime-devel] [CfP] European Lisp Symposium 2010
by Christophe Rhodes 13 Dec '09

13 Dec '09

Hi, I'm posting this call for papers to this list for two reasons: firstly, there are a lot of lisp developers and users on it, and I warmly encourage anyone to submit papers to this event. Secondly, in the context of this list, as well as the scope for paper writing I'd like to draw your attention to the possibility of submitting a proposal for a tutorial. Apologies to those who are receiving this call for the nth time. Cheers, Christophe 3rd European Lisp Symposium =========================== <http://www.european-lisp-symposium.org> May 6-7, 2010, Fundação Calouste Gulbenkian, Lisbon, Portugal Important Dates ~~~~~~~~~~~~~~~~ + Submission Deadline: *January 29, 2010* + Author Notification: March 1, 2010 + Final Paper Due: March 26, 2010 + Symposium: *May 6-7, 2010* We hope, as in previous years, to invite authors of accepted research contributions to submit an extended version of their papers to a special issue of the Journal of Universal Computer Science (J.UCS). Scope ~~~~~~ The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. The European Lisp Symposium 2010 invites high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives, all involving Lisp dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, and so on. Topics include, but are not limited to: + Language design and implementation + Language integration, interoperation and deployment + Development methodologies, support and environments + Reflection, protocols and meta-level architectures + Lisp in Education + Parallel, distributed and scientific computing + Large and ultra-large-scale systems + Hardware, virtual machine and embedded applications + Domain-oriented programming + Lisp pearls + Experience reports and case studies We invite submissions (through EasyChair) in two categories: original contributions and tutorials. * Original contributions should neither have been published previously nor be under review in any other refereed events or publication. Research papers should describe work that advances the current state of the art, or presents old results from a new perspective. Experience papers should be of broad interest and should describe insights gained from substantive practical applications. The programme committee will evaluate each contributed paper based on its relevance, significance, clarity, and originality. * Tutorial submissions should be extended abstracts of up to four pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. The programme committee will evaluate tutorial proposals based on the likely interest in the topic matter, the clarity of the presentation in the extended abstract, and the scope for interactive participation. The tutorials will run during the symposium on May 6, 2010. Programme Chair ~~~~~~~~~~~~~~~~ Christophe Rhodes, Goldsmiths, University of London, UK Local Chair ~~~~~~~~~~~~ António Leitão, Technical University of Lisbon, Portugal Programme Committee ~~~~~~~~~~~~~~~~~~~~ + Marco Antoniotti, Università Milano Bicocca, Italy + Giuseppe Attardi, Università di Pisa, Italy + Pascal Costanza, Vrije Universiteit Brussel, Belgium + Irène Anne Durand, Université Bordeaux I, France + Marc Feeley, Université de Montréal, Canada + Ron Garret, Amalgamated Widgets Unlimited, USA + Gregor Kiczales, University of British Columbia, Canada + Nick Levine, Ravenbrook Ltd, UK + Scott McKay, ITA Software, Inc., USA + Peter Norvig, Google Inc., USA + Kent Pitman, PTC, USA + Christian Queinnec, Université Pierre et Marie Curie, France + Robert Strandh, Université Bordeaux I, France + Didier Verna, EPITA Research and Development Laboratory, France + Barry Wilkes, Citi, UK + Taiichi Yuasa, Kyoto University, Japan

1 0

[slime-devel] point jumps around after copious output
by Stanislaw Halik 13 Dec '09

13 Dec '09

After lots of copious output, point tends to jump one screen backwards from the prompt. To reproduce: * Start SLIME with slime-repl, for example use my slime-setup line: (slime-setup '(slime-fancy slime-asdf slime-indentation slime-mdot-fu slime-package-fu slime-fancy slime-fontifying-fu slime-sprof)) * Input some command generating copious output, like (require 'foo) where FOO is some system for which fasls don't yet exist. * Remove focus from the REPL frame, so that the text scrolls down without the window moving. * When the system is done compiling and a new REPL prompt is drawn, the point will be moved one screen backward from the prompt. Requested behavior is prompt staying where it is.

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 13 Dec '09

13 Dec '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1934 slime/ChangeLog:1.1935 --- slime/ChangeLog:1.1934 Thu Dec 10 22:37:17 2009 +++ slime/ChangeLog Sat Dec 12 13:58:46 2009 @@ -1,3 +1,8 @@ +2009-12-12 Matthias Koeppe <mkoeppe(a)math.ucdavis.edu> + + * doc/slime.texi (Presentations): Add an example that illustrates + quoting necessary with presentations that are lists. + 2009-12-11 Stas Boukarev <stassats(a)gmail.com> * swank-allegro.lisp: Use new function `make-error-location'. Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.300 slime/contrib/ChangeLog:1.301 --- slime/contrib/ChangeLog:1.300 Fri Dec 11 01:35:20 2009 +++ slime/contrib/ChangeLog Sat Dec 12 13:43:29 2009 @@ -1,3 +1,14 @@ +2009-12-12 Matthias Koeppe <mkoeppe(a)math.ucdavis.edu> + + * slime-presentations.el (slime-reify-old-output): Revert change + of 2009-12-11, which introduced spurious quotes in non-evaluated + contexts like here: + + '(1 2 #<STANDARD-CLASS STANDARD-OBJECT> 3 4) + + Presentations do not change standard quoting rules; users just + need to remember this. + 2009-12-11 Stas Boukarev <stassats(a)gmail.com> * slime-fuzzy.el (slime-fuzzy-choices-buffer): Don't

1 0

[slime-devel] Lisp connection closed unexpectedly
by Plato Wu 13 Dec '09

13 Dec '09

Recently when I tried to start slime, most of the time it throw a error message: Connecting to Swank on port 45744.. [2 times] Lisp connection closed unexpectedly: connection broken by remote peer in *inferior-lisp* it shows: ;; Swank started at port: 45744. 45744 * ;; swank:close-connection: end of file on #<SB-SYS:FD-STREAM for "a socket" {B1593F1}> But I run slime again and don't create an additional inferior lisp, it works very well. I don't know why and can not get any debug information about it. I used Emacs 23.1.1, SLIME 2009-12-03, SBCL 1.0.31-2, my inferior-lisp-program is "/home/plato/clbuild/clbuild --implementation sbcl lisp" Thank you in advance!

7 12

[slime-devel] Daily ChangeLog diff
by Helmut Eller 12 Dec '09

12 Dec '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1928 slime/ChangeLog:1.1934 --- slime/ChangeLog:1.1928 Mon Dec 7 00:55:37 2009 +++ slime/ChangeLog Thu Dec 10 22:37:17 2009 @@ -1,3 +1,69 @@ +2009-12-11 Stas Boukarev <stassats(a)gmail.com> + + * swank-allegro.lisp: Use new function `make-error-location'. + (find-fspec-location): Handle errors. + Patch by Tobias C. Rittweiler. + +2009-12-11 Tobias C. Rittweiler <tcr(a)freebits.de> + + Add `M-x slime-toggle-debug-on-swank-error'. + + In "Debug on SWANK error" mode, errors which are normally caught + to not annoy the user, will now drop into the debugger. + + Additionally, the backend won't do any backtrace magic so you'll + see the full backtrace with all its glory details. (SBCL only so + far.) + + * slime.el (slime-toggle-debug-on-swank-error): New. + + * swank.lisp (toggle-debug-on-swank-error): New slimefun. + (debug-on-swank-error): New function. SETFable. + (invoke-default-debugger): Use CALL-WITH-DEBUGGER-HOOK so we're + trapped into the native debugger on SBCL (previously we weren't + due to SB-EXT:*INVOKE-DEBUGGER-HOOK*.) + + * swank.lisp: Rename SWANK-ERROR to SWANK-PROTOCOL-ERROR. + +2009-12-11 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-sbcl.lisp (call-with-debugger-hook): Oops, removed the + binding for *DEBUGGER-HOOK*. Fix that. + (make-invoke-debugger-hook): Do nothing if hook is NIL. + +2009-12-10 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-backend.lisp (*debug-swank-backend*): New variable. If + true, backends should not catch internal errors (e.g. during + definition finding), and should not perform backtrace magic. + (make-error-location): New helper. + (find-definitions [interface]): Default to error location. + + * swank-sbcl.lisp (converting-errors-to-location): New helper + macro. Regards new *DEBUG-SWANK-BACKEND*. + (find-definitions [implementation]): Use it. + (find-source-location [implementation]): Ditto. + (functiond-spec): Ditto. + (frame-source-location [implementation]): Ditto. + (*debug-definition-finding*): Removed. + (make-source-location-specification): Removed. + (safe-function-source-location): Removed. + (safe-source-location-for-emacs): Removed. Not needed anymore. + + (call-with-debugging-environment): Do not perform stack hinting + depending on *DEBUG-SWANK-BACKEND*. + +2009-12-10 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-sbcl.lisp (set-break-hook): New. + (call-with-break-hook): New, too. Both extracted from elsewhere. + (install-debugger-globally, call-with-debugger-hook): Use them. + (make-invoke-debugger-hook): Adapted not to call *debugger-hook* + on its own; it should rather decline because *debugger-hook* is + tried after *invoke-debugger-hook* anyway. Previously, a + custom *debugger-hook* (which declines itself) would have been + executed twice. + 2009-12-07 Stas Boukarev <stassats(a)gmail.com> * slime.el (slime-parse-toplevel-form): Use Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.296 slime/contrib/ChangeLog:1.300 --- slime/contrib/ChangeLog:1.296 Thu Dec 3 20:15:22 2009 +++ slime/contrib/ChangeLog Fri Dec 11 01:35:20 2009 @@ -1,3 +1,34 @@ +2009-12-11 Stas Boukarev <stassats(a)gmail.com> + + * slime-fuzzy.el (slime-fuzzy-choices-buffer): Don't + show cursor in *Fuzzy Completions*. + Patch by Tobias C. Rittweiler. + +2009-12-11 Stas Boukarev <stassats(a)gmail.com> + + * slime-presentations.el (slime-reify-old-output): Quote + the CL expession behind presentations, so _(1 2 3)_ (representing a + presentation) is not tried to be evaluated. + (slime-copy-presentation-to-repl): Use `looking-back' for looking back. + Apply De Morgan's law to conditions. + Patch by Tobias C. Rittweiler. + +2009-12-11 Stas Boukarev <stassats(a)gmail.com> + + * swank-asdf.lisp (find-operation): New function for + finding asdf operations independent of readtable + case sensitivity (read Allegro Modern Mode). + (operate-on-system): Accept symbols instead of strings for + operation-name, and use the above function. + + * slime-asdf.el: Replace strings with operation names + for `slime-oos' with symbols. + +2009-12-11 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-arglists.lisp (*swank-debug-arglists*): Removed. + (arglist-for-echo-area): Use DEBUG-ON-SWANK-ERROR instead. + 2009-12-04 Stas Boukarev <stassats(a)gmail.com> * swank-arglists.lisp (find-subform-with-arglist): Return

3 7

[slime-devel] Restore window configuration after closing a debug window.
by Nicolas Buduroi 10 Dec '09

10 Dec '09

Hi, I've been using slime casually for some time now and something always annoyed me, when the debug window pop up, it changes the size of the second window if there's one. I've searched for a ways to fix this behavior many times, but never found any simple solution. So today I've got myself into the code and made some changes. It works but the code is not really correct, one problem is that if you dig farther than the first cause and then use abort, it will hide the remaining debug buffers by restoring windows to their prior state. Can someone help me improve that code or show me a better way to achieve this? Here's the patch: --- slime.el.orig 2009-03-30 19:01:56.781250000 -0400 +++ slime.el 2009-12-10 00:28:27.984375000 -0500 @@ -1040,6 +1040,8 @@ (set-window-buffer popup-window old-buffer)))) (when (window-live-p selected-window) (select-window selected-window))) + (when sldb-last-window-configuration + (set-window-configuration sldb-last-window-configuration)) (kill-local-variable 'slime-popup-restore-data))) (defmacro slime-save-local-variables (vars &rest body) @@ -4069,6 +4071,8 @@ ;;(when msg (slime-insert-transcript-delimiter msg)) ;;(setq slime-repl-popup-on-output (not no-popups)) (setq cont (or cont #'slime-display-eval-result)) + (when (null sldb-last-window-configuration) + (setq sldb-last-window-configuration (current-window-configuration))) (slime-rex (cont (buffer (current-buffer))) (form) ((:ok value) (slime-eval-with-transcript-cont t value cont buffer)) ((:abort) (slime-eval-with-transcript-cont nil nil nil buffer)))) @@ -5158,6 +5162,9 @@ :group 'slime-debugger :type 'integer) +(defvar sldb-last-window-configuration nil + "Last window configuration before creating a new sldb buffer.") + ;;;;; Local variables in the debugger buffer Thanks

2 5

[slime-devel] startup problem
by Didier Verna 09 Dec '09

09 Dec '09

Hello, this morning, after an upgrade (although I'm not sure if it has anything to do with the problem), I start slime and I'm told: Version differ: 2009-10-19 (slime) vs. 2009-12-07 (swank). Continue ? If I say "yes", then I'm thrown into the *inferior-lisp* buffer, but I've got no slime repl. Any help would be appreciated ! -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com

3 4

[slime-devel] Possible typo in slime.texi; diff attached
by Iain Dalton 09 Dec '09

09 Dec '09

I saw what looked like a grammar error at [0], where some text seemed clipped off, and found the missing text at [1]. If the removal was an intentional change, the wording needs to be changed; otherwise, my diff will restore the missing text. [0]: http://common-lisp.net/project/slime/doc/html/Inspector.html [1]: http://www.wanglianghome.org/svn/elisp/3rd-party-lib/slime/doc/html/Inspect…

1 0

[slime-devel] Long running functions
by Elliott Slaughter 09 Dec '09

09 Dec '09

Hi, I'd like to interact with a running lisp process while it's executing a long-running function. Currently, any requests I make during the long running function call get pipelined until after the function call ends. As a contrived example, execute (sleep 10) at the REPL, then try to compile (C-c C-c) a function in another source file while Lisp is busy sleeping. I've been reading the manual page on swank communication style, and it sounds like the :spawn option does what I want. Unfortunately, thread support is not universal, and happens to missing on one of my main development platforms (SBCL on Windows). Is there any way I can work around this (e.g. add swank callbacks to my application)? I know this is kind of a long shot but it would be kind of nice to get this working independent of implementation thread support. Thanks. -- Elliott Slaughter "Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay

2 4