Re: ✨LeoJS beta 0.2.0 Released!

On Sunday, December 10, 2023 at 10:53:00 PM UTC-5 Félix wrote: For the web version, you have to have at least a repo created with at least one commit. Creating a new repo and also adding an automatic readme file inside of it while you create it do work if I recall correctly. (Totally new and

Re: ✨LeoJS beta 0.2.0 Released!

Thanks Thomas, Indeed I also noticed some problems with the importers (@auto) I've started an issue about .md markdown @auto imports failing. https://github.com/boltex/leojs/issues/60 Feel free to add an issue if you have details about the importers failing. For the web version, you have to

Re: ✨LeoJS beta 0.2.0 Released!

All right, it installed in vsc and it did open an outline. I saw a lot of errors like this: reading settings in C:/Users/tom/.leo/workbook.leo TypeError: Cannot read properties of undefined (reading 'trim') at Ini_Importer.find_blocks

Re: ✨LeoJS beta 0.2.0 Released!

I'm afraid I can't get started. The beta insists on opening a repo first, but I can't figure out how to either find my own repos or to get authenticated for Github. I'd rather start working on a .leo file that isn't in a repo at all. I'm never going to have all my outlines in a repo, but I

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:  LeoInteg 1.0.17 Released

On Sun, Dec 10, 2023 at 2:39 PM Félix wrote: *Announcing LeoInteg 1.0.17**! * Many thanks, Félix for all your work :-) 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,

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: PR #3678 merged into devel

On Friday, December 8, 2023 at 4:04:15 AM UTC-6 Edward K. Ream wrote: > Leo's devel branch now contains PR #3678 . > This PR improves the logic that reads external files and fixes bugs relating to the --blacken-sentinels command-line option.

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