> On May 18, 2017, at 6:38 AM, Christopher Allan Webber > <cweb...@dustycloud.org> wrote: > > Amirouche writes: > >> Le 27/02/2017 à 21:23, Andy Wingo a écrit : >>> On Sat 18 Feb 2017 20:59, Amirouche <amirou...@hypermove.net> writes: >>> >>>> How do you access variables in the REPL? >>> ,locals >>> >>> Andy >> It doesn't display something that I can use. > > (Returning to this few-months-old thread...) > > Yes, I frequently find that ,locals does not display much > information... it seems to be a toss-up whether the variables I need > will be contained in it, so I've reduced the amount I use the actual > debugger system in Guile a lot. A shame, because it seems really nice. > > Because of this, I think I do what a lot of Guile hackers do (which is > totally undocumented in the manual, so only people who have been hanging > around with someoen else who knows tend to know about it), which is to > use (pk) everywhere. It's not as nice as being able to play with local > variables at the REPL though!
> But then I ran ,optimize, and that made it obvious what's happening: > > (define (foo) > (start-repl > #:debug > (make-debug > (stack->vector (make-stack #t)) > 0 > "trap!" > #t)) > (start-repl Thanks for the insight. That explains a lot. Matt
