On Fri, Dec 23, 2011 at 1:32 PM, mdb <[email protected]> wrote: > I also wonder about the best work flow for developing or modifying a > plugin
There are two main approaches: 1. Restart Leo. I use a script called 'e.bat' that opens a private file (called ekr.leo). 2. If possible, you can use the so-called "stupendous aha" by creating an @test node that exercises your code, marking it, and then using Alt-5 (run-marked-unit-tests-externally). This way your work flow is edit, Alt-5, edit, Alt-5. Note that no saves are required: Alt-5 does this automatically for you. This only works if you *can* run your code externally, that is, if you aren't executing gui code. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
