Andy Wingo 5aa12c699c ,frame and related commands handle for-trap? appropriately ... * module/system/repl/debug.scm (print-frame): Add #:next-source? arg, for when print-frame should use frame-next-source instead of frame-source. (print-frames): Add #:for-trap? arg. If true, the 0th frame should be printed with frame-next-source. * module/system/repl/command.scm (define-stack-command): Introduce for-trap? into the lexical env. (backtrace, up, down, frame): Update to do the right thing regarding #:for-trap?.		2010-10-12 13:24:46 +02:00
..
command.scm	,frame and related commands handle for-trap? appropriately	2010-10-12 13:24:46 +02:00
common.scm	validating repl options; value-history on by default	2010-07-10 11:19:19 +02:00
debug.scm	,frame and related commands handle for-trap? appropriately	2010-10-12 13:24:46 +02:00
describe.scm	eval.c closures are now applicable smobs, not tc3s	2009-12-04 19:20:11 +01:00
error-handling.scm	debug has for-trap? field	2010-10-12 13:09:48 +02:00
repl.scm	further repl tweaks	2010-10-08 19:27:45 +02:00
server.scm	add (system repl server)	2010-10-10 12:15:34 +02:00