[slime-devel] too-eager *print-circle* binding in debugger
Test case: (error "~a" "duh") in terminal: debugger invoked on a SIMPLE-ERROR: duh in Slime: #1=#1# [Condition of type SIMPLE-ERROR] ...which is a bit suboptimal... Cheers, -- Nikodemus
2009/5/11 Nikodemus Siivola <nikodemus@random-state.net>:
Test case: (error "~a" "duh")
in terminal:
debugger invoked on a SIMPLE-ERROR: duh
in Slime:
#1=#1# [Condition of type SIMPLE-ERROR]
...which is a bit suboptimal...
Turns out this is partially my fault. I say partially because I'm pretty sure I don't deserve this for doing (drumroll...): (push '(*print-length* . nil) swank:*sldb-printer-bindings*) in .swank.lisp. I'm not doing that anymore -- but this still probably not intended behaviour. Cheers, -- Nikodemus
* Nikodemus Siivola [2009-05-16 11:10+0200] writes:
Turns out this is partially my fault. I say partially because I'm pretty sure I don't deserve this for doing (drumroll...):
(push '(*print-length* . nil) swank:*sldb-printer-bindings*)
in .swank.lisp. I'm not doing that anymore -- but this still probably not intended behaviour.
This should be fixed in HEAD. It was some hiccup with a custom printer table. Helmut.
On Sábado 16 Mayo 2009, Helmut Eller wrote:
* Nikodemus Siivola [2009-05-16 11:10+0200] writes:
Turns out this is partially my fault. I say partially because I'm pretty sure I don't deserve this for doing (drumroll...):
(push '(*print-length* . nil) swank:*sldb-printer-bindings*)
in .swank.lisp. I'm not doing that anymore -- but this still probably not intended behaviour.
This should be fixed in HEAD. It was some hiccup with a custom printer table.
Helmut.
I'm getting similar behaviour in the inspector. (defstruct aaa x y z) (make-aaa) Inspect the fresh struct object. Press return on one of the NILs and see three #1#=NILs upon return. Gabor
* Gábor Melis [2009-06-26 10:53+0200] writes:
I'm getting similar behaviour in the inspector.
(defstruct aaa x y z)
(make-aaa)
Inspect the fresh struct object. Press return on one of the NILs and see three #1#=NILs upon return.
This #1# means something different: it is supposed to inform you that the nil was already inspected before. It's indented for complicated object graphs when it is not obvious that the inspector "walks in a circle". Helmut.
participants (3)
-
Gábor Melis -
Helmut Eller -
Nikodemus Siivola