On Sun, Dec 10, 2023 at 8:08 AM Thomas Passin <[email protected]> wrote:
> > On Sunday, December 10, 2023 at 8:23:53 AM UTC-5 Edward K. Ream wrote: > > To see these in action, run a test program in *another* console. > > > This little tip is remarkably useful. Whether you are working on Leo code > or your own, each time you want to test a change run a new copy of Leo and > keep the original Leo session open. You can designate a particular outline > (often the workbook, the way I work) on the command line so the second Leo > session will open faster. > > You don't need to do this for a script that doesn't change code that Leo > uses, but otherwise test in a second session. You will have to close it > each time you make a correction, but you will keep your place in the code > in the original window, which would probably open more slowly as well. > Thanks Thomas. You have described my workflow exactly. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3FtXjepDkp4DmbfkFWtdzZa-UQ0Mr141feFLRGtoL-vA%40mail.gmail.com.
