On Thu, May 31, 2012 at 11:23 PM, anatoly techtonik <[email protected]>wrote:
> On Fri, Jun 1, 2012 at 2:59 AM, Jed Ludlow <[email protected]> wrote: > > On Thu, May 31, 2012 at 2:46 PM, Steve <[email protected]> > wrote: > >> > >> Also, can we get some hot keys for these actions? > > > > The global hot key space is getting pretty crowded. I'm open to > > recommendations on a set of global debugging hot keys that make sense. > > Recall that pdb already responds to "n" for next, "c" for continue, "s" > for > > step in, etc., when it has focus. > > Some unscientific research gathering information about debugging > shortcuts from different Python IDEs > (http://wiki.python.org/moin/IntegratedDevelopmentEnvironments) > definitely won't hurt here. Some scientific usability study would be > even more appreciated. =) Some IDEs have so-called 'debug mode', and I > suspect that if we don't have one, we may face a keyboard conflict > pitfall that this mode tries to avoid. I've added a page to Python > wiki with some into, as it is easier for everyone to edit. Feel free > to extend with your favorite editor combinations. > > http://wiki.python.org/moin/IDEKeyboardShortcuts > > In the spirit of Larry Tesler [1], I'd argue for staying modeless because it's not really clear that Spyder has a debugging mode per se. Most heavy-weight IDEs have a strong project-based model, so when you launch the debugger you really are debugging the current "project" as a glob of source files. On the other hand, in Spyder you can fire up a debugger at will on any script at any time. In fact, you could have several different interpreters open and running at the same time, each coming in and out of debugging interactively and independently. This high level of interactivity is what makes it so powerful for scientific computing. Strictly speaking the notion of "global" debugging commands is not really accurate since you have to designate which interpreter should receive the debugging commands by setting focus first. In that light, the global debugging toolbar and associated hot keys today would be implicitly understood to send commands to the interpreter that currently has focus. It's common to use function keys as hot keys for the basic debugging commands as Anatoly pointed out. If there really is enough demand for debugging hot keys to be somewhat inline with the model of other IDEs I guess we could reassign some of the less commonly used function keys to debugging commands, maybe in the F10-F12 range. Thoughts? [1] http://nomodes.com/Larry_Tesler_Consulting/CV.html -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
