The 2.5 debugger

[SimPLsol at aol.com]

Obviously the two commands that are the most important are Step Into and 
Abort.
Space and Option Space are utterly unintuitive. Command Period is also 
unintuitive but at least it is traditional.
A GUI where you have to go to the documentation (or get emails from the CEO - 
by the way, Thank You, Kevin) for simple things like shortcuts is not good 
use of a GUI.
Command I, Command T, and Command A are easy to remember because they relate 
to the action described by the button. I don't like Command R only because the 
button says Step Into; if the button was labeled Run, then Command R would be 
fine - but Step Into seems to describe the required action better.
As for Command I being used for Get Info and Command A being used for Select 
All, neither of those actions would ever be required in the debugger. There is 
a long history of Command Keys providing different shortcuts in different 
situations - how else could we run a modern graphics program with only 26 
shortcuts (half of which are already appropriated by the OS)?
I agree that Command Keys should be unique if possible, especially in 
situations where one might also be expecting the traditional action from the Command 
Key, but this is not the situation when debugging.
Please reconsider this before shipping the final 2.5.
Paul Looney