Helmut Eller heller@common-lisp.net writes:
- Tobias C. Rittweiler [2009-10-25 13:22+0100] writes:
If, now, you know that an error came from the same code path (often the case when you're interactively writing some part of your application), you can develop a good sense how restarts are numbered.
If it's from the same code path it will be numbered just the same because you will hit the same error again.
Yes, of course. I meant to say "similiar code path".
You mean, similar but yet different enough to trigger a different error but many restarts are still the same? How important is that case and how many restart would stay the same anyway?
SBCL does it, Slime does it, CLPython does it, unit test frameworks do it (stefil quite heavily, but also others live 5am or lift), web frameworks like UCW do it, probably others too.
Seems odd to optimize that case at the expense of making the top restarts harder to access.
It probably depends on how much you make use of frameworky stuff.
At the moment the cursor is placed at the first frame of the backtrace; we could make the cusor be placed at the first restart instead. (Perhaps also making TAB switch between restart list and backtrace.) This would make the restarts at the top easily accessible.
-T.