slime-devel December 2003

slime-devel@common-lisp.net

52 participants
93 discussions

[slime-devel] Problem with Slime/OpenMCL REPL
by Camille Troillard 18 Dec '03

18 Dec '03

Hi ! I was trying to simulate a break event in order to get the slime debugger buffer (*sldb*). I use the latest slime from the CVS. Here is the problem I got : 1. I started Emacs, then type M-x "slime" 2. after the CL-USER> prompt I type "(break)" Then I get the OpenMCL restarts : > Break in process Swank(2): > While executing: "Unknown" > Type :GO to continue, :POP to abort. > If continued: Return from BREAK. Type :? for other options. 1 > The problem is that I really can't get out of this, if I type ":pop" for instance, Emacs tell me that the "Text is read only". Then Emacs is stuck there, the only way to get out of this is to quit Emacs and restart. I sometimes get the same problem when pressing return or some other key without evaluating "(break)" ... I am sorry if this behaviour is normal, I am a Lisp newbie and I am still learning how to use the Emacs environment. Cheers, Camille

3 4

[slime-devel] Fonts in backtrace checked in
by Alan Ruttenberg 18 Dec '03

18 Dec '03

I can only test in openmcl, so if you don't mind please try this in some other lisp and see what happens. You need to enable it first by setting sldb-enable-styled-backtrace. -Alan * slime.el 1.155 Allow font choices for backtrace. Add group for customizing them: sldb. Whole thing is enabled with sldb-enable-styled-backtrace which is off by default, for now. Try '(sldb-condition-face ((t (:foreground "DarkSlateGray" :weight bold)))) '(sldb-detailed-frame-line-face ((t (:foreground "brown" :weight bold :height 1.2)))) '(sldb-local-name-face ((t (:weight bold)))) '(sldb-restart-face ((t (:foreground "DarkBlue" :weight bold)))) '(sldb-restart-number-face ((t (:underline t :weight bold)))) '(sldb-restart-type-face ((t (:foreground "DarkSlateGrey" :weight bold)))) '(sldb-section-face ((t (:weight bold :height 1.2)))) '(sldb-selected-frame-line-face ((t (:foreground "brown" :weight bold :height 1.2)))) '(sldb-topline-face ((t (:foreground "brown" :weight bold :height 1.2))))

2 1

[slime-devel] Clicky things in the REPL.
by lawrence mitchell 18 Dec '03

18 Dec '03

Having used the clim listener, I wondered if it would be possible to make things in the SLIME repl clicky in the same way that they are there. It turns out that this isn't too much of a problem, though the regexp horror was almost too much. I present herewith a minimal first example of use. Probably only works in SBCL, since that's what the regexp has been tested with, I don't know when the 'mouse-face text property was introduced in Emacs (or if it even exists in XEmacs), so, you might lose there, and I don't think that the 'keymap text property works in XEmacs. How it works: When the repl receives some output, it gets passed through SLIME-MAKE-CLICKY-THINGS, which looks for stuff of the form: #<name something> where something can have spaces in it. Then, depending on what NAME is, the relevant bit of the output is propertized, and inserted. Currently, it handles PACKAGE, FUNCTION, and foo-CLASS, the last is assumed to be a class of some kind. A local keymap is installed, which is accessible via mouse-3, and allows you to do things like describe the thing, or see it's documentation, etc... This requires one minor patch to swank.lisp, defining a DESCRIBE-PACKAGE function. Index: swank.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank.lisp,v retrieving revision 1.79 diff -u -r1.79 swank.lisp --- swank.lisp 14 Dec 2003 07:52:31 -0000 1.79 +++ swank.lisp 14 Dec 2003 21:44:31 -0000 @@ -724,6 +724,10 @@ (print-description-to-string (symbol-function (find-symbol-designator symbol-name)))) +(defslimefun describe-package (symbol-name) + (print-description-to-string + (find-package symbol-name))) + (defslimefun documentation-symbol (symbol-name &optional default) (let ((*package* *buffer-package*)) (let ((vdoc (documentation (symbol-from-string symbol-name) 'variable)) And the file itself: -- lawrence mitchell <wence(a)gmx.li>

8 13

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 18 Dec '03

18 Dec '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.170 slime/ChangeLog:1.175 --- slime/ChangeLog:1.170 Tue Dec 16 07:49:16 2003 +++ slime/ChangeLog Thu Dec 18 01:55:34 2003 @@ -1,3 +1,63 @@ +2003-12-17 Alan Ruttenberg <alanralanr(a)comcast.net> + * slime.el 1.155 + Allow font choices for backtrack. Add group for customizing them: sldb. + Whole thing is enabled with sldb-enable-styled-backtrace which is off by default, for now. + Try + '(sldb-condition-face ((t (:foreground "DarkSlateGray" :weight bold)))) + '(sldb-detailed-frame-line-face ((t (:foreground "brown" :weight bold :height 1.2)))) + '(sldb-local-name-face ((t (:weight bold)))) + '(sldb-restart-face ((t (:foreground "DarkBlue" :weight bold)))) + '(sldb-restart-number-face ((t (:underline t :weight bold)))) + '(sldb-restart-type-face ((t (:foreground "DarkSlateGrey" :weight bold)))) + '(sldb-section-face ((t (:weight bold :height 1.2)))) + '(sldb-selected-frame-line-face ((t (:foreground "brown" :weight bold :height 1.2)))) + '(sldb-topline-face ((t (:foreground "brown" :weight bold :height 1.2)))) + +2003-12-17 Alan Ruttenberg <alanralanr(a)comcast.net> + * slime.el 1.154 + Allow some face choices in the inspector. Try + '(slime-inspector-label-face ((t (:weight bold)))) + '(slime-inspector-topline-face ((t (:foreground "brown" :weight bold :height 1.2)))) + '(slime-inspector-type-face ((t (:foreground "DarkRed" :weight bold)))) + You can also set slime-inspector-value-face + +2003-12-17 Alan Ruttenberg <alanralanr(a)comcast.net> + + * swank-openmcl.lisp 1.40 + Fix an error with frame-source-location-for-emacs when the + function was a method-function. + Defined method-source-location that handles this case. You can + still end up looking at the wrong definition, as the protocol + doesn't allow passing back the qualifiers and specializers to look + up the correct one in the file + +. * swank-openmcl.lisp 1.39 + Allow you to continue after interrupting. + Properly set *swank-debugger-stack-frame* when interrupting. + + * slime.el 1.152 + sldb-continue now uses slime-oneway-eval + +2003-12-17 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el: Better handling of asynchronous output. + (slime-output-end): New variable. Use this marker to insert + output. Insert asynchronous output inserted before the "input + region" and before the prompt. + (slime-show-last-output): Use it. + (slime-repl-insert-prompt): Initialize it. + (slime-last-output-start): Removed. + (slime-flush-output): Increase delay to 20 usecs. + (slime-with-output-end-mark): Renamed from + slime-with-output-at-eob. Insert a newline if needed. + (slime-output-string, slime-repl-activate): Use it. + (slime-repl-return): Ensure that slime-repl-input-end-mark points + to a reasonable location. + +2003-12-17 Luke Gorrie <luke(a)bluetail.com> + + * HACKING: New file summarising our way of working. + 2003-12-16 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-lisp-preferred-package-nicknames): Removed. Not

1 0

[slime-devel] Re: Partial multiprocessing support on CMUCL
by Helmut Eller 17 Dec '03

17 Dec '03

Luke Gorrie <luke(a)member.fsf.org> writes: > Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > > > What do you think about Gary Byers comment that multi-threading support > > could be seen as a special case of multi-session support? > > > > Would it be easier if each thread had its own connection to Emacs? > > Each connection with its own state machine and buffers etc. > > I hadn't taken it in before -- I reread it and it does sound > appealing. With each Lisp thread having a separate socket, they > shouldn't have to do any synchronization amongst themselves for our > benefit. > > The first question that occurs is how to do the flow control. I > wonder if it could be done neatly by putting the "foreground" Emacs > network-process into asynchronous/process-filter mode, and switch the > others to synchronous I/O and not read from them? Hmm, not sure if I understand the problem. I think, if every thread has it's own connection with a separate state machine and associated buffers, we can do almost everything like we do now. We just have to make sure the we do it in the right buffer, something like per-session variables. And of course, we need a way to allow the thread to initiate the new connection. > > Also, by allowing more things to happen asynchronously, it seems like > we're getting more race-conditions and it could complicate the state > machine quite a lot. I'm starting to wonder if we could move some of > the state out of Emacs and into Lisp alone, so that it doesn't have to > be synchronized. I haven't got any good examples yet. Yes, if we have only one state machine on the Emacs side, it's probably better to move the protocol checking to the Lisp side. > BTW, I notice you replied privately -- better not to air too much > dirty laundry on the list, do you think? This was not intended, I must have pressed the wrong key. Helmut.

4 9

[slime-devel] checking protocol
by Alan Ruttenberg 17 Dec '03

17 Dec '03

I've been checking in changes (bugfixes for openmcl) and adding cvs comments but not editing the change log. Should I? I'd like to do some fontification of inspector and backtrace. So as not to offend anyone's taste I was thinking about having the default state for the faces be same as normal. For inspector I was thinking of 4 faces for the top line, type, label and value. For backtrace I haven't thought it through but I imagine error, restarts, function names, locals labels and values. Thoughts? -Alan

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 17 Dec '03

17 Dec '03

Index: slime/ChangeLog diff -u slime/ChangeLog:1.167 slime/ChangeLog:1.170 --- slime/ChangeLog:1.167 Mon Dec 15 14:13:53 2003 +++ slime/ChangeLog Tue Dec 16 07:49:16 2003 @@ -1,3 +1,29 @@ +2003-12-16 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-lisp-preferred-package-nicknames): Removed. Not + very interesting (and slightly broken) now that shortest-nicknames + are automatically used. + (slime-output-oneway-evaluate-request): New function to evaluate + an expression for side-effects (without getting a + result). + (slime-idle-state): Handle new :emacs-evaluate-oneway. + (slime-debugging-state): Handle :emacs-evaluate-oneway. + (sldb-invoke-restart): Use slime-oneway-eval. This avoids pushing + an evaluating state (which will be aborted, and print an unnecessary + message saying so). + (sldb-break-with-default-debugger): New command to break into the + default TTY debugger. Bound to 'B' in *sldb*. + (slime-read-string-state): Added :emacs-evaluate-oneway. + + * swank.lisp (invoke-nth-restart-for-emacs): Wrapper around + INVOKE-NTH-RESTART that checks that Lisp and Emacs agree on the + debug level. This detects and ignores old restart requests when + several are sent at once (possible because of new oneway-eval + feature). + (oneway-eval-string): New function to evaluate a string without + sending a result, and with *DEBUGGER-HOOK* bound to NIL. (The + debugger hook is inhibited to avoid state conflicts.) + 2003-12-15 Luke Gorrie <luke(a)bluetail.com> * swank-openmcl.lisp (ccl::*warn-if-redefine-kernel*): Support for

1 0

Re: [slime-devel] Re: Error starting slime after update
by Tim Lavoie 16 Dec '03

16 Dec '03

>>>>> "Luke" == Luke Gorrie <luke(a)member.fsf.org> writes: Luke> Ack.. Raymond Toy has had a similar problem. You can Luke> work-around it like this: Luke> (setq slime-log-events nil) Luke> It's some strageness in hideshow-mode, which we use in our Luke> *slime-events* buffer to "fold" sexps down to one-line Luke> summaries. That configuration change just turns off even Luke> logging. Hi Luke, That did it, thanks! -- "For every complex problem, there is an answer which is short, simple and wrong." -H.L. Mencken

1 0

[slime-devel] OpenMCL
by Sven Van Caekenberghe 16 Dec '03

16 Dec '03

Yesterday, we have been using SLIME on OpenMCL the whole day - and yes, we are happy ! Thank you all. However, there is a problem in the debugger connection in cvs head (as compared to the version we checked out 2 days ago): an undefined function like (foo) gives an (presumably emacs) error: error in process filter: Assertion failed: (<= (length frames) maximum-length) - and as far as we understand SLIME, everything is broken/lost then. It is a bit hard to use SLIME without entering the lisp debugger ;-) One of the reasons that we like SLIME so much is the fact that it doesn't choke on asynchroneous output (as ILISP does): when working with a multithreaded server that makes all the difference in the world. The output that non-evaluator threads write to stdout goes to the inferior lisp buffer, we can live with that, but maybe it would be nicer if (optionally) that output was inserted in the normal SLIME REPL buffer (maybe in some other color) - is that possible, maybe the behavior is different on other platforms ? Also, on one machine, some of the output is 'undecorated', on an other it looks like this: ^@^@\213(:read-output "127.0.0.1 - - [Fri, 12 Dec 2003 08:51:02 GMT] \"GET /ha-dynsite/webaction?action=show-current-calendar HTTP/1.1\" 200 -1 ") Where does the difference come from ? Are only some streams redirected properly ? Thx, Sven

7 19

[slime-devel] sldb-continue
by Alan Ruttenberg 16 Dec '03

16 Dec '03

I added a "continue" restart so that you could continue after interrupting in openmcl. The thing is that when you do continue you get a "Evaluation aborted" message in the minibuffer, (but evaluation proceeds properly). How do I repair this? -Alan

2 2

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel December 2003