Re: print_depth

Sabastian,

>When debugging, the term print depth defaults to 5

This is correct. I don't think there is a way to change this default.

The reason that it is default to 5 is that in general, with larger print
depths, the goal become so large that you can't usefully visually inspect it.
The idea is that if you want to examine a goal in more detail, you would use
the inspect subterm facilities to do so: when you come to the goal you are
interested in and it has a large structure you want to examine, then you step
into it using inspect subterm. Have you use this before, or is it not
suitable for you?

>The manual describes this incorrectly, I think.

Which part of the manual is incorrect? We would like to fix it if it is wrong.
I just looked at the debug chapter of the user manual, and it does correctly
say that the debugger has its own private print depth, different from the
global setting...

>I am quite a happy user of the command line interface of Eclipse, but

Might I suggest you try TkECLiPSe? The debugger has many nice features not
found (or possible) in the command line interface, although you also can
set the debug print depth default there.

Cheers,

Kish Shen