But note that LeoInteg still relies on Leo having already been installed,
since it must start the LeoBridge and a headless Leo executable.
On Friday, May 12, 2023 at 3:46:19 PM UTC-4 Thomas Passin wrote:
Felix will say more, but LeoInteg, running as an addon in VSCode, talks to
Leo via the
Felix will say more, but LeoInteg, running as an addon in VSCode, talks to
Leo via the LeoBridge to ascertain the state of the tree and the contents
of Leo's nodes. So it's like a repeater in a way, and you can work with
the tree and body in LeoInteg instead of Leo's Qt panes. Leo commands
Hmm, interesting idea. I've never used vs-code (I'm not a programmer). Is
this documented anywhere how this might work? I've seen references to
Felix's work on leointeg but never really understood what the point was.
Rob...
Otoh, the simplest way to use Leo nowadays is to click the leoInteg
leoInteg isn't able to handle some plugins and the in-tab apps I've been
writing lately, IIUC.
On Friday, May 12, 2023 at 6:34:30 AM UTC-4 Edward K. Ream wrote:
> On Thu, May 11, 2023 at 11:45 PM Thomas Passin wrote:
>
>> I just tried making a self-contained Leo installer for Windows with
>>
On Thu, May 11, 2023 at 11:45 PM Thomas Passin wrote:
> I just tried making a self-contained Leo installer for Windows with
> PyInstaller. the executable failed with this error:
Thanks for your investigation. Let's see what we can do for the next
release.
Otoh, the simplest way to use Leo
I just tried making a self-contained Leo installer for Windows with
PyInstaller. the executable failed with this error:
File "leo\core\leoApp.py", line 1853, in reportDirectories
g.es(f"{kind:>10}:", os.path.normpath(theDir), color='blue')
