On Sunday, December 10, 2023 at 7:00:12 AM UTC-6 Edward K. Ream wrote: > Imo, LeoPyRef.leo is the *only* reasonable starting point for study. Forget the documentation. It describes the code's *results*.
But once you read Leo's sources, it's time to dive in! First, create a new git branch based on devel. This branch will contain your work. Don't even think about programming without git. It's the essential safety net. Next, get comfortable with *g.trace(g.callers())* and *breakpoint*, a Python primitive. Run Leo from a console for these. If you like, add traces or breakpoints to Leo's code to see how Leo works. To see these in action, run a test program in *another* console. The hard part is getting started. *Expect *to put ten units in for every unit out. It's the only way. You'll gain momentum soon enough. 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/fbe0a10d-d5ab-4d6c-8f6b-52adb4f4d280n%40googlegroups.com.
