Luke Gorrie wrote:
Sundar Narasimhan sundar@itasoftware.com writes:
BTW -- following up on this. I may not have my mental model quite right yet -- if I type several 'n' or 'p' in SLDB -- and then type in the REPL loop -- should I expect to (or not) get eval-in-frame semantics right
No. Only the commands named `in-frame' will actually evaluate in the specific frame. Everything else, including REPL input, will just be EVAL'd in the null lexical environment from deep in the debugger loop.
I have a feeling that people are expecting different behaviour, but I'm not sure exactly what. Please feel free to spell it out.
Hi, Luke -- I wonder if there should be a "set-frame-in-repl" command.. which when invoked.. will make these evaluations occur in the specific frame. I know you mentioned C-u : and C-u e, but the former seems not to eval in frame, and the latter goes to the minibuffer. What I think I would like is to do a 'set-frame' and then just c-x o to the other window and continue to interact there.. which will avoid a lot of the limitations associated with having limited screen real estate in the minibuffer area. Does that make sense?
- I notice that c-c c-m (macroexpand) does not seem to work
correctly wrt. packages.. for example in cmu lisp -- it inserts common-lisp-user: rather than the package the form appears in.
It does the right thing in the examples I've tried. More details?
Ok.. We have code that essentially does a (in-package :xyz) at the top of the file. Unfortunately I have a habit of moving to a particular form, and then macro expanding it to see the code. When I do this in slime mode.. I get global variables and other things prefixed with common-lisp-user::. But when I actually cut-paste (macroexpand 'myform) or (macroexpand1 'myform) in the repl .. I don't get this .. any idea on what could be happening?
<>Is there an equivalent of reparse-attribute-list? I'm not familiar with that, what's it do?
On certain machines.. :) emacs would, if you had a line like so at the top of your file.. ;;;-*- Mode: Lisp; Package: foo; -*-
M-x reparse-attribute-list setup the evaluation context to do the appropriate thing. In ilisp -- this is similar to set-buffer-package-lisp?
<>
- When I type 'r' within sldb I get the foll.. how do I get to
restart a frame.. w/ the same arguments as originally invoked..?
No matching method for the generic function #<STANDARD-GENERIC-FUNCTION SWANK-BACKEND:RESTART-FRAME (0)
This ugly message really means that the RESTART-FRAME feature is not implemented for CMUCL. I would like to improve such messages but it's at least slightly tricky, as I believe is supporting that feature.
Yes.. I just realized cmucl doesn't have this -- thanks :)
-Luke
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel