Stepper should permit better navigation of steps

The other frustrating thing that I find about the Stepper is that it is so difficult to navigate to the part of the stepping we care about. I understand that the Stepper is not the full debugger, but the navigation of the debugger is much easier to use because you can easily set breakpoints and then choose to go into or over expressions.

In the Stepper, you can choose to "jump" to the next application step, but you can only do that once. I have found no way to repeat this (on 6.7, but I think 6.10 is similarly affected). Once I jump to the next application step I can only move forward one step at a time, which means it takes a long time to find the steps I actually care about. There is some functionality called "Jump to beginning of selected" but I do not know how to activate this.

I can think of a few possible solutions to this, but I do not know what is easiest to implement:

• Maybe you could make the full debugger available in the teaching languages, but that doesn't fix the Stepper itself.
• Maybe you could allow the jump functionality to be applied multiple times (perhaps with a "jump" button?). I am not sure whether this would jump fast enough that users could navigate to the expressions they care about or not.
• Maybe you could implement functionality to jump a particular number of steps. Maybe being able to jump by 10 steps or 50 steps (or a user defined number of steps) would help students zoom in on the step they care about faster.
• Maybe you could add some kind of breakpoint functionality without reimplementing the full debugger.

It would be nice (although not a complete solution) to be able to put breakpoint in front of a check-expect and step from that point, but my understanding is that this would be awkward to implement. Students currently take the expression out of the check-expect and put it into the definitions window, then step from there. That is an awkward workaround, but it kind of works.

Maybe this is user error and I don't know what I am doing. In that case is there documentation that could help me?

Start by reproducing the Stepper navigation behavior described for DrRacket 6.7 and 6.10, including jumping to the next application step and stepping from a check-expect expression. Review the existing Stepper and debugger behavior before choosing among repeated jumps, step counts, breakpoints, or documentation. Done requires an agreed navigation behavior and tests or documentation showing how students reach the expressions they need.