Re: recommend an approach or path to learning more about Leo

> > My Last Lecture will probably say surprisingly little about programming. > That's good, we're curious about anything about the father of Leo -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: recommend an approach or path to learning more about Leo

> Btw, your daily workflow is also a great info item as I asked before > . You > don't need to think too much about what to teach us, just do what you want > to do, and I think it must be valuable. > Will do. My Last Lecture

Re: recommend an approach or path to learning more about Leo

> > Leo's info items > collect such knowledge. Be sure to check the closed items. > Wow! > This thread has inspired me to create my own Last Lecture > as an info item. Stay > turned. >

Re: recommend an approach or path to learning more about Leo

On Sun, Dec 10, 2023 at 6:35 PM HaveF HaveF wrote: > I found that there are a lot of tricks scattered in the forums. I wondered, would it be better to collect all this content? Leo's info items collect such knowledge. Be sure to check the

Re: recommend an approach or path to learning more about Leo

On Mon, Dec 11, 2023 at 3:06 AM Thomas Passin wrote: > Another big benefit of using a second Leo session is if you are working on > core Leo code and you make a mistake that prevents Leo from running. If > you only used the one Leo window, you are in trouble because you won't be > able to start

Re: recommend an approach or path to learning more about Leo

On Sunday, December 10, 2023 at 9:08:27 AM UTC-5 Thomas Passin 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. ... You don't need to do this for a script that doesn't change code that Leo uses,

Re: recommend an approach or path to learning more about Leo

> > > 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. > Nice tip! Thanks!

Re: recommend an approach or path to learning more about Leo

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

Re: recommend an approach or path to learning more about Leo

> > 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

Re: recommend an approach or path to learning more about Leo

> > I meant to say, *breakpoint*(). > It does not work well on my Mac. It constantly output: QCoreApplication::exec: The event loop is already running [image: image.png] -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from

Re: recommend an approach or path to learning more about Leo

On Sun, Dec 10, 2023 at 8:08 AM Thomas Passin 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

Re: recommend an approach or path to learning more about Leo

On Sunday, December 10, 2023 at 7:23:53 AM UTC-6 Edward K. Ream wrote: > Don't even think about programming without git. Here are some "looking over my shoulder" tips related to workflow: *Leo's git-related commands and scripts* I frequently use Leo's *git-diff* (*gd*) and *git-diff-pr*

Re: recommend an approach or path to learning more about Leo

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

Re: recommend an approach or path to learning more about Leo

On Sunday, December 10, 2023 at 7:23:53 AM UTC-6 Edward K. Ream wrote: Next, get comfortable with *g.trace(g.callers())* and *breakpoint*, a Python primitive. I meant to say, *breakpoint*(). My myLeoSettings.leo defines the bp;; abbreviation as: breakpoint() ### The ### reminds me to

Re: recommend an approach or path to learning more about Leo

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

Re: recommend an approach or path to learning more about Leo

Nice. Thanks for your advice, Edward, Thomas, and Jake! -- -- Sincerely, HaveF -- 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

Re: recommend an approach or path to learning more about Leo

On Sat, Dec 9, 2023 at 8:02 AM HaveF HaveF wrote: I'm eager to expand my knowledge of Leo. While reading code is a viable > learning method, I find the scope of Leo overwhelming. Could you recommend > an approach or path to learning more about Leo that is *manageable and > not too steep*? >

Re: recommend an approach or path to learning more about Leo

Leo programming can definitely be a challenge. It's tempting to say "go look at plugin X", for example, but what's really needed is a way to find out how to do things, how to discover the right existing part of Leo's code base, and how to go about the work effectively. There isn't anything

Re: recommend an approach or path to learning more about Leo

Hi, Jake, Thanks for your idea. I do like learning deeply, but step by step. I mean, I don't want learning curve 'too steep' [image: image.png] On Sat, Dec 9, 2023 at 10:14 PM Jacob Peck wrote: > "Too deep" is definitely a bit subjective, and will vary by person. > > But what I found

Re: recommend an approach or path to learning more about Leo

"Too deep" is definitely a bit subjective, and will vary by person. But what I found helpful is to build a few plugins. Find some pocket of your workflow that you think could be just a little bit better 'if ' and write a plugin that does . Plugins are a good way, imo, to limit your

recommend an approach or path to learning more about Leo

Hello, I have mastered the basics of Leo and am using it daily this year. I can use Leo to manage contents, write commands, create buttons, and even develop a small interface on the Log/Find/Tags/Nav panel. However, I'm not satisfied and wish to delve deeper into Leo. I have an idea to