Re: Use the bridge, Luke

On Tue, Jun 18, 2019 at 6:27 PM Terry Brown wrote: Then I'm not sure that there's really anything to do. Python's > well integrated into vim, so you can just use leoBridge as usual. Cool. > I guess I can do something to verify that, but I can't see why it > wouldn't work. > Please do.

Re: Problem when trying to upgrade a version of Leo in an existing VE to Leo 6.0 beta 1

On Wed, Jun 19, 2019 at 12:44 AM Viktor Ransmayr wrote: > As I reported yesterday into the announcement thread of Leo 6.0 beta 1 > installation into a **new** virtual environment using pip & PyPI is working > as well. > > However, when I tried to install Leo 6.0 beta 1 into **existing* virtual

Problem when trying to upgrade a version of Leo in an existing VE to Leo 6.0 beta 1

As I reported yesterday into the announcement thread of Leo 6.0 beta 1 installation into a **new** virtual environment using pip & PyPI is working as well. However, when I tried to install Leo 6.0 beta 1 into **existing* virtual environments I ran into trouble. - See attached logs. @Matt

Re: Use the bridge, Luke

On Tue, 18 Jun 2019 17:20:37 -0500 "Edward K. Ream" wrote: > On Tue, Jun 18, 2019 at 2:22 PM Terry Brown > wrote: > > > > Thanks. I didn't know that. In that case the entire vim plugin > > > would be based on this > > > . Care to give it > > > a

Re: Use the bridge, Luke

On Tue, Jun 18, 2019 at 2:22 PM Terry Brown wrote: > > > Thanks. I didn't know that. In that case the entire vim plugin would > > be based on this . > > Care to give it a go? > > Not without much more specific objectives ;-) > The objective is

Re: Leo 6.0 beta 1 released. Please do *not* commit to devel

Hello Edward & Matt, Am Di., 18. Juni 2019 um 17:05 Uhr schrieb Edward K. Ream : > > The GitHub release is here. Some minor issues will be fixed asap, so please > continue to hold all commits to devel. > > Many thanks to the Team Leo members who helped make this version a success. > > The

Re: Use the bridge, Luke

On Tue, 18 Jun 2019 11:31:30 -0700 (PDT) "Edward K. Ream" wrote: > > > On Tuesday, June 18, 2019 at 12:38:51 PM UTC-5, Terry Brown wrote: > > > > A lot of vim plugins are written in Python, so perhaps you could > > use that instead of vimscript. > > > > Thanks. I didn't know that. In that

More reasons why Leo won't emulate pyzo

It's important to complete the pyzo project as much as possible. As part of this process, this post lists more reasons why I have no intention of ever integrating pyzo into Leo. - It's dead easy to switch back and forth between pyzo and Leo. - I personally would not use pyzo's shell. - Pyzo's

Re: Use the bridge, Luke

On Tuesday, June 18, 2019 at 12:38:51 PM UTC-5, Terry Brown wrote: > > A lot of vim plugins are written in Python, so perhaps you could use that > instead of vimscript. > Thanks. I didn't know that. In that case the entire vim plugin would be based on this

Re: Use the bridge, Luke

A lot of vim plugins are written in Python, so perhaps you could use that instead of vimscript. Cheers -Terry On Tue, Jun 18, 2019 at 12:07 PM Edward K. Ream wrote: > Integrating pyzo into Leo fails because pyzo's shell can't control Leo's > gui. However, such scripts *could *access the data

Use the bridge, Luke

Integrating pyzo into Leo fails because pyzo's shell can't control Leo's gui. However, such scripts *could *access the data in Leo outlines using Leo's bridge . That is, Leo's bridge supports *restricted Leonine scripts*. This in no way tempts me to embed

Re: Anyone having troubles seeing git revs

On Tuesday, June 18, 2019 at 10:10:53 AM UTC-5, Edward K. Ream wrote: I've attempted a fix in devel. Please pull the latest rev (b8fe3e1). Then run Leo with --trace=startup and report the results. Edward -- You received this message because you are subscribed to the Google Groups

Re: Rethinking Leo 6.1 and pyzo integration

On Tue, Jun 18, 2019 at 9:49 AM john lunzer wrote: I dislike having multiple editors/IDEs open because it is often messy and > the "integrated" component of IDE gets lost. > Imo, letting pyzo be pyzo and Leo be Leo is as clean a division of labor as can be imagined. In practice, it would be

Re: Rethinking Leo 6.1 and pyzo integration

On Tue, Jun 18, 2019 at 10:05 AM Chris George wrote: The python terminal plugin has never worked for me as it causes Leo to > segfault every time I enabled it. > I've just created #1212 for this. This should end the dithering about whether

Re: Anyone having troubles seeing git revs

On Tue, Jun 18, 2019 at 10:05 AM lewis wrote: > Here it is: > lewis@Argon MINGW64 /n/git/leo-editor/leo/core (devel) > $ git log -n 1 > commit f203a28564b0d8f8e09a2e54f74a325f00f69a88 (HEAD -> devel, > origin/devel) > Author: Edward K. Ream > Date: Tue Jun 18 03:31:03 2019 -0500 > > Added

Re: Rethinking Leo 6.1 and pyzo integration

The features from the file browser are nice but as you stated before you can include them in the Leo file browser easier than trying to integrate existing pyzo code. Back when I started down the path of trying to learn python a couple of years ago, Leo's lack of an integrated shell drove me to

Re: Anyone having troubles seeing git revs

Here it is: lewis@Argon MINGW64 /n/git/leo-editor/leo/core (devel) $ git log -n 1 commit f203a28564b0d8f8e09a2e54f74a325f00f69a88 (HEAD -> devel, origin/devel) Author: Edward K. Ream Date: Tue Jun 18 03:31:03 2019 -0500 Added comment about autocompleter plugins [end] Lewis -- You

Leo 6.0 beta 1 released. Please do *not* commit to devel

The GitHub release is here . Some minor issues will be fixed asap, so please continue to hold all commits to devel.

Re: Rethinking Leo 6.1 and pyzo integration

I dislike having multiple editors/IDEs open because it is often messy and the "integrated" component of IDE gets lost. I'm not implying that you do more work; it is your Leo, we just use it. I'm not optimistic that users would see this as a "good" or "clean" solution to having shell and file

Re: Anyone having troubles seeing git revs

On Tue, Jun 18, 2019 at 8:26 AM lewis wrote: Can you please clarify? You want me to run 'git log -n 1' from a git > console as shown below? > Yes. It's almost certainly failing. I want us both to see the actual os message. That should help you get git log working, which is what Leo needs.

Re: Anyone having troubles seeing git revs

Can you please clarify? You want me to run 'git log -n 1' from a git console as shown below? *MINGW64 /n/git/leo-editor/leo/core (devel)* *$* Regards Lewis > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

Re: Anyone having troubles seeing git revs

On Tue, Jun 18, 2019 at 5:06 AM lewis wrote: > Running commit f203a28. > In the console: > > N:\git\leo-editor>launchleo.py --trace=startup > No. You are to run *this* in the console: git log -n 1 Edward -- You received this message because you are subscribed to the Google Groups

Re: Anyone having troubles seeing git revs

Running commit f203a28. In the console: N:\git\leo-editor>launchleo.py --trace=startup reading settings in N:/git/leo-editor/leo/config/leoSettings.leo reading settings in C:/Users/lewis/.leo/myLeoSettings.leo Empty setting name in False set parent @settings reading settings in

Re: Rethinking Leo 6.1 and pyzo integration

On Tuesday, June 18, 2019 at 1:28:51 AM UTC-5, Edward K. Ream wrote: > In short, adding pyzo's features to Leo would be really really stupid. *Port mortem* It hurts to have spent months on a fool's errand. Otoh, the pyzo project did drive the two main features of Leo 6.0, namely moving to

Re: Team Leo

On Tuesday, June 18, 2019 at 2:12:22 AM UTC-5, Zoom.Quiet wrote: My Chinese name? -> 周琦 > Thanks. I've acknowledged you with both this and Zoom.Quiet. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

Re: Team Leo

Edward K. Ream 于2019年6月18日周二 下午1:39写道： > > > > On Mon, Jun 17, 2019 at 8:16 PM Zoom.Quiet wrote: >> >> Edward K. Ream 于2019年6月18日周二 上午12:26写道： > > >> i always worry abt. that issue is real help for Leo? > > > No need to worry. You have added a lot to Leo. > > Am I correct in assuming that your

Rethinking Leo 6.1 and pyzo integration

Leo 6.1 supposedly would integrate pyzo features into Leo. See this page. In fact, doing so would be foolish and unnecessary, as I shall now explain. *Doh: Read the documentation, Luke* A few