On Sunday, December 10, 2023 at 9:26:06 AM UTC-5 iamap...@gmail.com 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. Thank you Thomas, your explanation is very, very clear. I get the point. I forgot to say that I run the second Leo session using a theme with a different color scheme from the first one. That way I don't get mixed up and make a change in or close the wrong window. You can set a specific theme with the --theme= command line parameter. -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ed458b79-25af-4e49-ba68-447f166ce4a9n%40googlegroups.com.
