🚀 go-pugleaf

It is, but only one command at a time.

Actually, it's not too bad working with BBedit. I leave the file open and if I remember to leave a corner of its window visible at bottom right below my palettes, I can just fire it up again by clicking on it. Failing that, option-double-click on the script name in the palette and there it is.

Then, save, click on the ID document, shift-double-click the script name in the palette and there I am in the debugger. A bit of a bugger, though, if I want to keep setting the same breakpoints each time.

Maybe there should be a way of encoding a breakpoint into the script itself, perhaps in a special form of comment so that if you don't fire up the debugger it is ignored.

Dave