Provide option for all trees to be closed by default.

[chasingmaxwell]

This enables faster browsing when you have large objects and arrays that come before the variable(s) you are actually interested in.

[hobbes3]

Yes, but as far as I know, Vdebug doesn't "remember" which trees should be opened or closed after you step over, so it might be annoying to keep re-opening trees.

[chasingmaxwell]

I think it depends on the situation. For instance, I find it annoying to have to keep closing trees every time I step over. At least with an option you would have the ability to determine this behavior for yourself.

[joonty]

You can already do this actually, since it's a feature of Xdebug: set the max_children feature to be 0:

:let g:vdebug_features['max_children'] = 0

I believe that 1 is the default value, but you can set it to whatever you like - it only affects the initial retrieval. Take a look at http://xdebug.org/docs-dbgp.php#feature-names.

[chasingmaxwell]

I tried setting max_children to 0 which did give me closed trees by default, but then I was not able to open them. Curiously, the behavior when I double-click the closed tree is to remove the uninitialized variable underneath it, but the tree does not open.

[joonty]

You're right, it does mess up. I'll take a look into this - thanks.

[joonty]

I'm taking this out of version 1.4.1, as I want to get that out of the door. I'll return to it after the release.

Thanks

[danjamin]

👍 collapsed option would make debugging much easier for me as well

[narcoclepsy]

I'd favor the collapse. a "remember what was expanded / collapsed" tree would be amazing but I can imagine the difficulty in such an implementation.