* Tobias C. Rittweiler [2009-10-25 14:53+0100] writes:
Helmut Eller heller@common-lisp.net writes:
[...]
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.
Does what?
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.
At the cost of making the first frame harder to find and wasting keys 0..3 for stuff that's already covered by q.
If the restart at the bottom are so important those people could just make their custom keybindings.
Obviously my sense for aesthetics is just odd. I'll shut up now.
Helmut