Idea for the browsing pipe

[moodymudskipper]

I think it can work a bit like the other special features.

When we hit the %B>% pipe in the call stack we switch the global variable browsing, when browsing is switched on we get to browse after each call, but where ?

We could wrap the *RETURN_CALL* in a function and debug there when browsing is switched on. When continuing we'd just get to the next browser call and so on (maybe no way to get out of all browser calls at once)

See if impact on speed is dramatic.