>>The issue of timers while debugging is actually quite frustrating, when various screen candy comes with so many of them - toolbars using them to refresh, statusbar likewise, hover buttons having their own... and if you turn the debugger on, all that code executes visibly slower and you have to wait... but then it executes again because some of the timers are set to 100ms. It's a nightmare. So something like killtimers.prg is necessary, saves some nerves at times.
>
>With the keyboard shortcut I can disable the debugger when I forgot to before running code, and vice versa, I can still add breakpoints which then will be or won't be respected. I have also been able to escape from endless loops in some cases, but not always.

Now that's something - I don't really care whether I can escape an endless loop, killing the process costs almost nothing nowadays, but being able to jump in and see when/where it happens is worth it. Just stepping through a few rounds of it would lead to a solution much faster than any other way (specially not if it happens near the end of a longer process). How did you set up that shortcut?

...never mind, found it, at the very end :).