slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Backtrace verbosity
by Lars Magne Ingebrigtsen 02 May '04

02 May '04

I've been using Slime for a couple of days now, and it seems really spiffy and snappy. Things generally just are much faster and easier than in ILISP, which I used before. The backtrace doesn't feel quite right, though: Backtrace: 0: SWANK::DEBUG-IN-EMACS (#<DIVISION-BY-ZERO 506820FC>) 1: SWANK:SWANK-DEBUGGER-HOOK (#<DIVISION-BY-ZERO 506820FC> :DONT-KNOW) 2: DBG::DEBUG1 (NIL #<DIVISION-BY-ZERO 506820FC> NIL NIL) 3: INVOKE-DEBUGGER (NIL (#<DIVISION-BY-ZERO 506820FC>)) 4: CONDITIONS::CONDITIONS-ERROR (:INVISIBLEP T DIVISION-BY-ZERO (:OPERATION / :OPERANDS (1 0))) 5: SYSTEM::DIVISION-BY-ZERO-ERROR (/ 1 0) 6: / (NIL NIL NIL) 7: SPECIAL::%EVAL-NOHOOK ((/ 1 0)) 8: IV:PROCESS-TOP-LEVEL (DSPEC:*CURRENT-FORM* #S(LEXICAL::ENVIRONMENT LEXICAL::VARIABLES NIL LEXICAL::FUNCTIONS NIL LEXICAL::REMOTE-ENVIRONMENT NIL) #<function LEXICAL:EVAL-WITH-ENV 502BFB7A> NIL :EXECUTE) 9: SWANK::EVAL-REGION ("(/ 1 0) " NIL T) 10: SWANK::REPL-EVAL ("(/ 1 0) ") 11: SWANK:LISTENER-EVAL ("(/ 1 0) ") (This is from evaluating (/ 1 0).) Point is placed on frame zero, which means that the real error is five lines below, and I find it annoying that I have to search visually down to it to get to it. So I'd either suggest that frames 0-4 are hidden by default, or that (at least) the point is placed on line 5. -- (domestic pets only, the antidote for overdose, milk.) larsi(a)gnus.org * Lars Magne Ingebrigtsen

2 2

[slime-devel] Inferior Lisp won't die bug
by David Steuber 01 May '04

01 May '04

This is a case of unexpected behavior. It could also be a nasty case of user error. It's also possible that this is an SBCL bug. If that is the case, I can report the issue on sbcl-devel. I don't want to cross post so I'm trying here first. What I expected was for the inferior lisp process to shut down. Info: david@vega:~ $ uname -a Linux vega 2.6.5-k7 #1 SMP Thu Apr 29 10:01:49 EDT 2004 i686 GNU/Linux ; SLIME 2004-05-01 CL-USER> (loop for i from 1 to 10 collect (* i i) ) (1 4 9 16 25 36 49 64 81 100) CL-USER> (quit) ; Evaluation aborted Looks good so far, but... *inferior-lisp* This is SBCL 0.8.10.4, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. ; loading system definition from ; #P"/home/david/usr/lib/sbcl/systems/sb-bsd-sockets.asd" into ; #<PACKAGE "ASDF2757"> ; registering #<SYSTEM SB-BSD-SOCKETS {9912B21}> as SB-BSD-SOCKETS ; registering #<SYSTEM SB-BSD-SOCKETS-TESTS {9D71FB1}> as SB-BSD-SOCKETS-TESTS ; loading system definition from ; #P"/home/david/usr/lib/sbcl/systems/sb-posix.asd" into #<PACKAGE "ASDF2857"> ; registering #<SYSTEM SB-POSIX {985B089}> as SB-POSIX ; registering #<SYSTEM SB-POSIX-TESTS {99A0689}> as SB-POSIX-TESTS * STYLE-WARNING: implicitly creating new generic function STREAM-READ-CHAR-NO-HANG STYLE-WARNING: implicitly creating new generic function STREAM-READ-CHAR-WILL-HANG-P WARNING: discarding unsupported DOCUMENTATION of type SYMBOL for object SYMBOL WARNING: These Swank interfaces are unimplemented: (DISASSEMBLE-FRAME LIST-CALLEES LIST-CALLERS PROFILE-PACKAGE RESTART-FRAME WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) T * ;; Swank started at port: 32898. 32898 * (quit) debugger invoked on a SIMPLE-ERROR in thread 24022: Syscall interrupt_thread failed: No such process You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) (SB-THREAD:INTERRUPT-THREAD 2 24026 QUIT)[:EXTERNAL] 0] (sb-ext:quit) debugger invoked on a SB-INT:SIMPLE-CONTROL-ERROR in thread 24022: attempt to THROW to a tag that does not exist: SB-IMPL::%END-OF-THE-WORLD You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Reduce debugger level (to debug level 1). (SB-KERNEL::UNSEEN-THROW-TAG-ERROR-HANDLER 4 #<unavailable argument> #.(SB-SYS:INT-SAP #X40386BF8) #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X403868C8 :TYPE (* (STRUCT SB-VM::OS-CONTEXT-T-STRUCT))> (142))[:EXTERNAL] 0[2] After this, I can't do M-x slime again and have it work. Not even if I do M-x slime-disconnect. Doing the perhaps friendlier M-x slime-disconnect to exit a session doesn't kill the inferior lisp process either: *inferior-lisp* 0[2] * ;; Swank started at port: 32907. 32907 * ;; Connection to Emacs lost. ;; [end of file on #<FILE-STREAM for "a constant string" {9790839}>] (quit) debugger invoked on a SIMPLE-ERROR in thread 24147: Syscall interrupt_thread failed: No such process You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) (SB-THREAD:INTERRUPT-THREAD 2 24150 QUIT)[:EXTERNAL] 0] (sb-ext:quit) debugger invoked on a SB-INT:SIMPLE-CONTROL-ERROR in thread 24147: attempt to THROW to a tag that does not exist: SB-IMPL::%END-OF-THE-WORLD You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Reduce debugger level (to debug level 1). (SB-KERNEL::UNSEEN-THROW-TAG-ERROR-HANDLER 4 #<unavailable argument> #.(SB-SYS:INT-SAP #X40386BF8) #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X403868C8 :TYPE (* (STRUCT SB-VM::OS-CONTEXT-T-STRUCT))> (142))[:EXTERNAL] 0[2] ;; Swank started at port: 32911. 32911 0[2] That last Swank started message was from doing M-x slime. If I do a M-x slime-disconnect and then a M-x slime-connect, I am unable to reconnect to the inferior lisp process. Typing (quit) in the repl is probably not a friendly thing to do. I don't know how difficult it would be to know to close the inferior lisp process so that it can be started fresh with another M-x slime command. Perhaps an M-x slime-end-session or something would be a nice thing? Or is the general preference to just exit Emacs and start over? -- I wouldn't mind the rat race so much if it wasn't for all the damn cats.

2 2

[slime-devel] Some more variables for customizing Slime (patch)
by Lars Magne Ingebrigtsen 01 May '04

01 May '04

Hi. I just started using Slime twenty minutes ago, and here's a patch to, er, make it look like I want it to. *** ChangeLog.~1.357.~ Thu Apr 29 00:25:05 2004 --- ChangeLog Thu Apr 29 11:34:06 2004 *************** *** 1,3 **** --- 1,12 ---- + 2004-04-29 Lars Magne Ingebrigtsen <larsi(a)netfonds.no> + + * slime.el (slime-event-buffer-name): New variable. + (slime-events-buffer): Use it. + (slime-space-information-p): Ditto. + (slime-space): Use it. + (slime-reply-update-banner-p): Ditto. + (slime-repl-update-banner): Use it. + 2004-04-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * swank-loader.lisp (*lisp-name*): Add versioning support for *** slime.el.~1.282.~ Wed Apr 28 18:45:01 2004 --- slime.el Thu Apr 29 11:33:59 2004 *************** *** 114,119 **** --- 114,128 ---- "Function to use for translating Lisp filenames to Emacs filenames. See also `slime-translate-to-lisp-filename-function'.") + (defvar slime-event-buffer-name "*slime-events*" + "The name of the Slime event buffer.") + + (defvar slime-space-information-p t + "Whether the SPC key should offer information or not.") + + (defvar slime-reply-update-banner-p t + "Whether Slime should keep a repl banner updated or not.") + ;;; Customize group *************** *** 1665,1672 **** (goto-char (point-max))))) (defun slime-events-buffer () ! (or (get-buffer "*slime-events*") ! (let ((buffer (get-buffer-create "*slime-events*"))) (with-current-buffer buffer (set (make-local-variable 'outline-regexp) "^(") (set (make-local-variable 'comment-start) ";") --- 1674,1681 ---- (goto-char (point-max))))) (defun slime-events-buffer () ! (or (get-buffer slime-event-buffer-name) ! (let ((buffer (get-buffer-create slime-event-buffer-name))) (with-current-buffer buffer (set (make-local-variable 'outline-regexp) "^(") (set (make-local-variable 'comment-start) ";") *************** *** 1821,1827 **** (expand-file-name default-directory)))) ;; Emacs21 has the fancy persistent header-line. (cond ((boundp 'header-line-format) ! (setq header-line-format banner) (pop-to-buffer (current-buffer)) (when (fboundp 'animate-string) ;; and dancing text --- 1830,1837 ---- (expand-file-name default-directory)))) ;; Emacs21 has the fancy persistent header-line. (cond ((boundp 'header-line-format) ! (when slime-reply-update-banner-p ! (setq header-line-format banner)) (pop-to-buffer (current-buffer)) (when (fboundp 'animate-string) ;; and dancing text *************** *** 1830,1836 **** 0 0))) (slime-repl-insert-prompt "")) (t ! (slime-repl-insert-prompt (concat "; " banner)) (pop-to-buffer (current-buffer)))))) (defun slime-init-output-buffer (connection) --- 1840,1849 ---- 0 0))) (slime-repl-insert-prompt "")) (t ! (slime-repl-insert-prompt ! (if slime-reply-update-banner-p ! (concat "; " banner) ! "")) (pop-to-buffer (current-buffer)))))) (defun slime-init-output-buffer (connection) *************** *** 3247,3253 **** more than one space." (interactive "p") (self-insert-command n) ! (when (and (slime-connected-p) (or (not (slime-busy-p)) ;; XXX should we enable this? ;; (not slime-use-sigint-for-interrupt)) --- 3260,3267 ---- more than one space." (interactive "p") (self-insert-command n) ! (when (and slime-space-information-p ! (slime-connected-p) (or (not (slime-busy-p)) ;; XXX should we enable this? ;; (not slime-use-sigint-for-interrupt)) *************** *** 5409,5415 **** (def-slime-selector-method ?v "the *slime-events* buffer." ! "*slime-events*") (def-slime-selector-method ?l "the most recently visited lisp-mode buffer." --- 5423,5429 ---- (def-slime-selector-method ?v "the *slime-events* buffer." ! slime-event-buffer-name) (def-slime-selector-method ?l "the most recently visited lisp-mode buffer." *************** *** 6000,6006 **** "Kill all the slime related buffers. This is only used by the repl command sayoonara." (dolist (buf (buffer-list)) ! (when (or (member (buffer-name buf) '("*inferior-lisp*" "*slime-events*")) (string-match "\*slime-repl\[\d+\]\*" (buffer-name buf)) (string-match "\*sldb .*\*" (buffer-name buf))) (kill-buffer buf)))) --- 6014,6021 ---- "Kill all the slime related buffers. This is only used by the repl command sayoonara." (dolist (buf (buffer-list)) ! (when (or (member (buffer-name buf) '("*inferior-lisp*" ! slime-event-buffer-name)) (string-match "\*slime-repl\[\d+\]\*" (buffer-name buf)) (string-match "\*sldb .*\*" (buffer-name buf))) (kill-buffer buf)))) -- (domestic pets only, the antidote for overdose, milk.) larsi(a)gnus.org * Lars Magne Ingebrigtsen

4 4

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 01 May '04

01 May '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.358 slime/ChangeLog:1.360 --- slime/ChangeLog:1.358 Fri Apr 30 02:40:17 2004 +++ slime/ChangeLog Fri Apr 30 20:10:40 2004 @@ -1,3 +1,20 @@ +2004-05-01 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (sldb-abort): Print a message if the Emacs RPC + returns. It shouldn't, if ABORT manages to unwind the stack, but + it currently does in OpenMCL due to some bug. + (slime-edit-definition-fallback-function): Name of a function to + try if the builtin edit-definition finding fails. You can set + this to `find-tag' to fall back on TAGS. + + * swank.lisp (list-all-systems-in-central-registry): Use explicit + :wild in pathname for matching (needed in at least SBCL). + + * swank-openmcl.lisp: Removed obsolete `swank-compile-system'. + + * swank-sbcl.lisp: Removed obsolete `swank-compile-system'. + Removed some stale comments about supported features. + 2004-04-30 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-repl-update-banner): Don't print the working

1 0

[slime-devel] ABORT restart in OpenMCL not working
by Luke Gorrie 30 Apr '04

30 Apr '04

Howdy, If you fire up SLIME in OpenMCL and pull up SLDB (e.g. with (/ 1 0)) then it seems the ABORT restart ('a') doesn't work. Invoking it seems to just return nil instead of aborting the evaluation. Anyone know what's up?

3 2

Re: [slime-devel] Re: NEWS
by Bill_Clementson＠peoplesoft.com 30 Apr '04

30 Apr '04

Luke Gorrie <luke(a)bluetail.com> writes: > Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > > > Today we received bugreports like "CLISP hangs on startup", "SBCL dies > > with SIGBUS", "can't set FPU modes". Desn't seem like SLIME is ready > > for release and making a tarball will not help us getting there. > > I agree. Our current rock&roll development style makes this all pretty > easy to handle: "Foo is broken [here's a patch]." "Fixed in CVS now." > Much more fun than "That'll be fixed in the next release." > > The important thing is to make the best Emacs programming mode known > to man in the fastest and most enjoyable way. The rest is secondary. > > But thanks Brian for the vote of confidence in the current maturity! > However, I think having cautious people avoid SLIME initially is a > much lesser evil than having them download it thinking it's more > mature than it really is and then curse and swear at it. > > BTW, SLIME is the most fun project I've been involved in and I > attribute much of this to everyone using the same CVS code. With 31 > hackers listed in the ChangeLog we must be doing something right :-) I agree with Brian that SLIME is mature enough for a release. However, I also agree with Luke that it's more fun working with the CVS copy. The reasons that most people want a release are: 1. Some people don't like downloading out of CVS and prefer a tarball. 2. A release provides a "fixed" snapshot that you can be pretty sure works (more or less) 3. A release says to the world "We're ready for users now" I don't know if these reasons really apply to SLIME. For #1, as Helmut has mentioned, it is possible to download a tarball of the current CVS SLIME from: http://common-lisp.net/cgi-bin/viewcvs.cgi/cvs_root.tar.gz?tarball=1&cvsroo… This effectively negates #1. It might be worthwhile to mention the tarball in the docs and/or CLiki so that CVS-adverse users aren't scared away. Reason #2 isn't really that important either, since the turn-around on bugs is so quick :-). For the super-wary, the FAIRLY-STABLE download provides an alternative. Is a tarball of the FAIRLY-STABLE code available also? Reason #3 is a subjective consideration. I know that I held off trying SLIME for a long time because I thought it was still a work-in-progress and not ready for production use. However, there are a lot of people recommending SLIME now and I would say that it has the highest mindshare of the Emacs CL modes. You guys just have to learn to bite your tongues and stop saying it isn't mature enough yet ;-) The downside to producing a release is that you encourage people to take the "stable" release as opposed to the "flaky" CVS version. This divides users and means that there are fewer eyes checking the latest code. When you have a stable, slow-changing product, this is ok. However, since there is so much active (and enthusiastic) development on SLIME, I'd say there isn't a lot of benefit in producing a "Release" yet. - Bill

3 2

[slime-devel] NEWS
by Luke Gorrie 30 Apr '04

30 Apr '04

Ahoy, I added a file called NEWS. Here we can record interesting user-visible changes to SLIME in a digest format so that users can learn about new features. I'm thinking this is worthwhile because it'd take a fair bit of work to fully track the mailing list and ChangeLog these days. The idea is that each time we release^Wmove the FAIRLY-STABLE tag we can send the current NEWS section to the list and start a new section in the file. Cheers, Luke

4 4

[slime-devel] Showing running output
by Lars Magne Ingebrigtsen 30 Apr '04

30 Apr '04

If calling a function such as (defun test-function () (loop for i from 1 to 10 do (format t "~a~%" i) (sleep 1))) in the repl, I get a whole lot of nothing, and then after ten seconds, I get the output. Which is natural, because the output stream is buffering. So the obvious (*ahem*) thing to do is: (setf (slot-value (slot-value (slot-value *terminal-io* 'system::output-stream) 'stream::buffer-state) 'stream::output-limit) 1) which fixes the problem. But surely this isn't supposed to be necessary. (This is with LispWorks 4.2.7 and current CVS Slime.) -- (domestic pets only, the antidote for overdose, milk.) larsi(a)gnus.org * Lars Magne Ingebrigtsen

2 2

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 30 Apr '04

30 Apr '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.357 slime/ChangeLog:1.358 --- slime/ChangeLog:1.357 Wed Apr 28 18:25:05 2004 +++ slime/ChangeLog Fri Apr 30 02:40:17 2004 @@ -1,3 +1,38 @@ +2004-04-30 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-repl-update-banner): Don't print the working + directory. It rarely fits in a line and was only Emacs' + default-directory. M-x pwd is convenient enough. + + * swank.lisp (symbol-indentation): Don't infer indentation for + symbols starting with 'def' or 'with-'. It was wrong most of the + time and Emacs' defaults are better. + + * swank-lispworks.lisp (emacs-connected): Add methods to + stream-soft-force-output for socket-streams and + slime-output-streams. This flushes those streams automatically + (i assume it gets called when Lisp is idle). + +2004-04-29 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-repl-mode): Set slime-current-thread to + :repl-thread. + + * swank.lisp (thread-for-evaluation, dispatch-event): Accept + :repl-thread as thread specifier and dispatch evaluation and + interrupt request properly. + (repl-thread-eval, repl-eval): Deleted. We do the special casing in + thread-for-evaluation. + +2004-04-29 Lars Magne Ingebrigtsen <larsi(a)netfonds.no> + + * slime.el (slime-event-buffer-name): New variable. + (slime-events-buffer): Use it. + (slime-space-information-p): Ditto. + (slime-space): Use it. + (slime-reply-update-banner-p): Ditto. + (slime-repl-update-banner): Use it. + 2004-04-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * swank-loader.lisp (*lisp-name*): Add versioning support for

1 0

[slime-devel] More newbie questions: process-interrupt in LispWorks
by Lars Magne Ingebrigtsen 29 Apr '04

29 Apr '04

As far as I can tell, `C-c C-c' in the REPL gives me a rather uninformative backtrace, but doesn't actually interrupt the currently evaluating form. Which is kinda disappointing. So how do you break the form that's running? -- (domestic pets only, the antidote for overdose, milk.) larsi(a)gnus.org * Lars Magne Ingebrigtsen

2 2

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