Re: Team Leo

[Zoom.Quiet]

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 name is 写道?  I would like to add your 
> proper name.
>

My Chinese name? -> 周琦
but there is s many same name word in China,
so if point me, please usage:
Zoom.Quiet (周琦)

because Zoom.Quiet is global unique, but 周琦 is not unique,
had to bind for identification ...

BTW:
foe translation document for Lep,
we call u as:
令德华(Edward K. Ream)

PS:
写道 <-- means: write as

> 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 post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/leo-editor/CAMF8tS2Cx8SY8NqoS27C%2BSmjNJudHe8krr%3DfF942fN_AM_XgWA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
life is pathetic, go Pythonic! 人生苦短, Python当歌!
俺: http://zoomquiet.io
授: http://creativecommons.org/licenses/by-sa/2.5/cn/
怒: 冗余不做,日子甭过!备份不做,十恶不赦!
KM keep growing environment culture which promoting organization learning!

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAAFijRcxpK05aNBUToawE0sB%3DargnZzmqeWK_p%3DAg50HHWT3bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Team Leo

[Edward K. Ream]

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 stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/8be5aa1c-d086-4149-8efe-23e5e58d1672%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rethinking Leo 6.1 and pyzo integration

[Edward K. Ream]

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 Python 3 and 
supporting Qt docks.  Both are important and useful.

Anyway, we can't change the past, and it's good to acknowledge our mistakes 
and move on.  The belated Aha's will prevent even more wasted effort in 
future.  It's good to see how easy it is for Leo and pyzo to work together.

So now I personally am at a big transition.  None of the items scheduled 
for 6.1 are urgent.  They could easily be postponed for months, or even to 
the end of this year. It's time for a big rethink of where I go next.  This 
should be exciting, if a bit daunting. It's been decades since I have been 
in this situation.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ecbcb367-0900-4ea1-b464-4910b63bf4b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone having troubles seeing git revs

[lewis]

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 C:/Users/lewis/.leo/LeoBlackGraySolarized.leo
Exception in g.getGitVersion
Traceback (most recent call last):

  File "N:\git\leo-editor\leo\core\leoGlobals.py", line 4992, in 
getGitVersion
shell=True,

  File 
"C:\Users\lewis\AppData\Local\Programs\Python\Python37\lib\subprocess.py", 
line 395, in check_output
**kwargs).stdout

  File 
"C:\Users\lewis\AppData\Local\Programs\Python\Python37\lib\subprocess.py", 
line 487, in run
output=stdout, stderr=stderr)

subprocess.CalledProcessError: Command 'git log -n 1 --date=iso' returned 
non-zero exit status 1.

Exception in g.getGitVersion
Traceback (most recent call last):

  File "N:\git\leo-editor\leo\core\leoGlobals.py", line 4992, in 
getGitVersion
shell=True,

  File 
"C:\Users\lewis\AppData\Local\Programs\Python\Python37\lib\subprocess.py", 
line 395, in check_output
**kwargs).stdout

  File 
"C:\Users\lewis\AppData\Local\Programs\Python\Python37\lib\subprocess.py", 
line 487, in run
output=stdout, stderr=stderr)

subprocess.CalledProcessError: Command 'git log -n 1 --date=iso' returned 
non-zero exit status 1.

Leo 6.0-devel, devel branch
livecode.py: can not import meta
you can install meta with `pip install meta`
rss.py: can not import feedparser
load_session loading: C:/Users/lewis/.leo/workbook.leo
reading settings in C:/Users/lewis/.leo/workbook.leo
DynamicWindow.__init__ workbook.leo
restoreWindowState workbook.leo found key: 
windowState:C:/Users/lewis/.leo/workbook.leo
startup time:  3.72 sec
[end]

Regards
Lewis

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/3da1a488-d499-481b-9534-9e3c50e979af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone having troubles seeing git revs

[Edward K. Ream]

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 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS1v3jCmJqx8WVoYiwKxU0Uv9zeghwpAES3Y6-d%3D4VkQjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone having troubles seeing git revs

[lewis]

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 stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/a145b45f-3a57-4c1f-97ec-39f8d7c18935%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone having troubles seeing git revs

[Edward K. Ream]

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.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2tL2ryiPns%3DuLZJQkQ2JD8hVKPjTE9qi%3DPDn9Pi8BqmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rethinking Leo 6.1 and pyzo integration

[john lunzer]

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 browser features available to them.

I am, however, implying that your Doh/Aha moment might be a personal one 
and that the desire for the stated features to be integrated *within* Leo 
will not go away because of it.

That said thank you for the recent work, very much appreciated.

On Tuesday, June 18, 2019 at 2:28:51 AM UTC-4, Edward K. Ream wrote:
>
> 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 days ago I had a sickening Doh! moment.  I have done extensive 
> code-level prototyping of pyzo integration without having a clear idea of 
> what pyzo does!  I'm talking about the *basics*, covered in the pyzo intro 
> , configuring shells 
>  and interactive vs script mode 
> .
>
> From the pyzo intro: "Shells run in a sub-process, such that when it is 
> busy, Pyzo itself stays responsive, allowing you to keep coding and even 
> run code in another shell."
>
> This explains why pyzo uses yoton, and the related complexity.  yoton 
> allows pyzo to show results in the "Workspace", "History Viewer" and 
> "Shell" areas, while the actual computation happens in an external process.
>
> So far, so good.  What are the implications?
>
> My first thought was that Leo could easily adapt the Ctrl-B logic to run 
> code in an external process.  But just a bit more thought shows that that 
> won't work.  *Scripts run in an external environment can't be Leonine*. 
> They could be given access to c, g and p, but they could not control Leo 
> without heroic measures.
>
>
> *Doh: Pyzo can run alongside Leo*
>
> Yesterday I saw this clearly for the first time. It was another 
> sickeningly obvious "revelation".  
>
> Pyzo does a great job of showing and updating external files.  So anyone 
> can get the benefits of both Leo and Pyzo *right now* as follows:
>
> 1. Use Leo to create and update external files, as usual.
> 2. Use pyzo to open files and run shells, as desired.
>
> In short, adding pyzo's features to Leo would be really really stupid.
>
> *Summary*
>
> Anyone can get the benefits of Leo and pyzo by running them side by side.  
> Doh!
>
> I shall not add pyzo's major features to Leo.  Not in 6.1.  Not ever.
>
> Suddenly, Leo looks finished as well as complete :-)  It's time to 
> investigate new directions for Leo with more playful prototypes.
>
> All comments welcome and encouraged.
>
> 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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/3faacace-ddbf-4f91-8c17-86fec0d0e196%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 highlights of Leo 6.0*

   - Leo now requires python 3.6 or above.
   This greatly simplifies Leo's code.
   - Leo's default gui uses Qt Docks.
   Use --no-dock to use Leo's legacy gui.
   - Several commands now generate clickable links in the Log pane.
   This greatly speeds navigation.
   - The usual assortment of bug fixes and minor improvements.

*Links*

   - Leo's home page: http://leoeditor.com
   - Documentation 
   - Tutorials 
   - Video tutorials 
   - Forum 
   - Download 
   - Leo on GitHub 
   - LeoVue 
   - What people are saying about Leo 
   
   - A web page that displays .leo files 
   
   - More links 

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/2f300f9d-8829-47ef-a17f-1a3f2d196c62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone having troubles seeing git revs

[lewis]

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 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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/0957f6c1-aaca-4a8c-bc68-7c37af88fa9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rethinking Leo 6.1 and pyzo integration

[Chris George]

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 pyzo. The python
terminal plugin has never worked for me as it causes Leo to segfault every
time I enabled it.

And would it not make sense to make the shell an iPython shell instead of
just the regular one?

Chris

On Tue, Jun 18, 2019 at 7: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.
>
> 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 browser features available to them.
>
> I am, however, implying that your Doh/Aha moment might be a personal one
> and that the desire for the stated features to be integrated *within* Leo
> will not go away because of it.
>
> That said thank you for the recent work, very much appreciated.
>
> On Tuesday, June 18, 2019 at 2:28:51 AM UTC-4, Edward K. Ream wrote:
>>
>> 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 days ago I had a sickening Doh! moment.  I have done extensive
>> code-level prototyping of pyzo integration without having a clear idea of
>> what pyzo does!  I'm talking about the *basics*, covered in the pyzo
>> intro , configuring shells
>>  and interactive vs script mode
>> .
>>
>> From the pyzo intro: "Shells run in a sub-process, such that when it is
>> busy, Pyzo itself stays responsive, allowing you to keep coding and even
>> run code in another shell."
>>
>> This explains why pyzo uses yoton, and the related complexity.  yoton
>> allows pyzo to show results in the "Workspace", "History Viewer" and
>> "Shell" areas, while the actual computation happens in an external process.
>>
>> So far, so good.  What are the implications?
>>
>> My first thought was that Leo could easily adapt the Ctrl-B logic to run
>> code in an external process.  But just a bit more thought shows that that
>> won't work.  *Scripts run in an external environment can't be Leonine*.
>> They could be given access to c, g and p, but they could not control Leo
>> without heroic measures.
>>
>>
>> *Doh: Pyzo can run alongside Leo*
>>
>> Yesterday I saw this clearly for the first time. It was another
>> sickeningly obvious "revelation".
>>
>> Pyzo does a great job of showing and updating external files.  So anyone
>> can get the benefits of both Leo and Pyzo *right now* as follows:
>>
>> 1. Use Leo to create and update external files, as usual.
>> 2. Use pyzo to open files and run shells, as desired.
>>
>> In short, adding pyzo's features to Leo would be really really stupid.
>>
>> *Summary*
>>
>> Anyone can get the benefits of Leo and pyzo by running them side by
>> side.  Doh!
>>
>> I shall not add pyzo's major features to Leo.  Not in 6.1.  Not ever.
>>
>> Suddenly, Leo looks finished as well as complete :-)  It's time to
>> investigate new directions for Leo with more playful prototypes.
>>
>> All comments welcome and encouraged.
>>
>> 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 post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/3faacace-ddbf-4f91-8c17-86fec0d0e196%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CADWQas2TWF2vdoXTS9UD-mrcVn7agHPmNswB0StCh7AbnqO5hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone having troubles seeing git revs

[Edward K. Ream]

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 comment about autocompleter plugins
> [end]
>

Thanks.  The cause of your troubles isn't clear.  Leo thinks this command
is failing, but clearly it isn't.  Presumably there is a problem with the
result code from mingw.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS27ZYiznk%3DDbgxED9Ui9%3D%3D3nPFAOXQDqQg%3D1G2Bx0nSqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rethinking Leo 6.1 and pyzo integration

[Edward K. Ream]

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 this plugin is worth resuscitating.
It is.

> And would it not make sense to make the shell an iPython shell instead of
> just the regular one?
>

I don't think so.  If you want IPython, try --ipython.  This is a pretty
nifty feature. It integrates Leo and IPython as much as possible.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS17JeG21mYtQN1EaWH8EisN%3DQxkhOj7C%2BBDb6GJHfFVdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rethinking Leo 6.1 and pyzo integration

[Edward K. Ream]

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 rare to have both pyzo and Leo
open at the same time.  But that would "just work" if you actually do that.

Integrating pyzo's shell (and related features) simply doesn't work.
Scripts run from the pyzo shell aren't (can't be) Leonine scripts.  That
being so, it makes more sense to use pyzo if you you want pyzo's features.

I'm not optimistic that users would see this as a "good" or "clean"
> solution to having shell and file browser features available to them.
>

Then we'll have to educate them.  Or better, get the python_terminal plugin
working.

...your Doh/Aha moment might be a personal one and that the desire for the
> stated features to be integrated *within* Leo will not go away because of
> it.
>

It's not going to happen.  Get used to it.

Life is too short to add mostly useless features.  It's time to do
something interesting :-)

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS1X%2Bi3HAcDsQvSx%3DJ5n7pi1b5-UV_ZR37wbB81Td-Dknw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone having troubles seeing git revs

[Edward K. Ream]

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 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/8361d804-024e-4a70-abe0-bb94f08c7cfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Use the bridge, Luke

[Edward K. Ream]

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 
pyzo's shell, debugger, etc. into Leo ;-)

It is easy to start Leo's bridge from pyzo, or IPython, or any other python 
environment. It's an alternative to leo --ipython, for example.

I have just created #1213 
: support Leo's 
bridge in vim.  This would be a separate from Leo's vim.py plugin, and 
might have advantages for some vim users. It would be written in vim script 
. Anyone interested in this project? I'll be 
glad to answer any questions you may have.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/2a72fe65-4817-40fa-b48a-32902dfce416%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use the bridge, Luke

[Terry Brown]

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 in Leo outlines using 
> Leo's
> bridge .  That is, Leo's bridge
> supports *restricted Leonine scripts*.  This in no way tempts me to embed
> pyzo's shell, debugger, etc. into Leo ;-)
>
> It is easy to start Leo's bridge from pyzo, or IPython, or any other
> python environment. It's an alternative to leo --ipython, for example.
>
> I have just created #1213
> : support Leo's
> bridge in vim.  This would be a separate from Leo's vim.py plugin, and
> might have advantages for some vim users. It would be written in vim
> script . Anyone interested in this
> project? I'll be glad to answer any questions you may have.
>
> 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 post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/2a72fe65-4817-40fa-b48a-32902dfce416%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAFPg46RGnJR7qO%2BF0uwtyAWo8n2URR5d_n5s5xphyp0qYGR8ug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use the bridge, Luke

[Edward K. Ream]

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 .  Care to 
give it a go?

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c79b0504-49f4-413e-99ff-18ee24bac8be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

More reasons why Leo won't emulate pyzo

[Edward K. Ream]

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 shell isn't a great match for Leo's script composition features.  
The distinction between interactive and script mode 
 pretty much doesn't exit in 
Leo.

- Leo's plugins can already do almost everything pyzo does. Sure, they 
might be improved, maybe using actual pyzo code.  But this is hardly a high 
priority item.

- The pyzo_support plugin does a lot of heavy lifting.  Feel free to 
experiment with it, if you think the work is worth *your* time.

*Summary*

If you want pyzoic features, use pyzo. You can access Leo outlines from 
pyzo using Leo's bridge.

Leo can always be improved, perhaps using pyzo's ideas, or even code.  But 
that's very different from "importing" pyzo's shell architecture.  It's 
just not worth doing.

More work on this pyzo integration is not worth my time. It's time for new 
directions.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/7f2b23a0-84f0-41b3-8713-2a4cd53eaa08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use the bridge, Luke

[Terry Brown]

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 case the entire vim plugin would
> be based on this .
> Care to give it a go?

Not without much more specific objectives ;-)

vim doesn't always come with Python support installed, but I'm guessing
more often than not.  Also it's not hard to compile vim from scratch,
so in cases where Python's missing, it's probably not hard to add.

Given that, I don't think any RPC / client-server vimscript <->
leo_bridge_server.py plumbing would be worth the effort, just write the
vim part in Python, and therefore just use leoBridge as usual.

So then what?  vim can use a Leo file as a data structure, but how does
it navigate the Leo file?  vim's https://github.com/scrooloose/nerdtree
and https://github.com/majutsushi/tagbar#screenshots plugins both
implement tree navigation, but I haven't looked at either enough to
know if they can be re-purposed.  I feel that this looks like possibly
low hanging fruit, but would turn into a bigger project.  And there are
other options for editing Leo files.  Leo, for example ;-)

Cheers -Terry

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/20190618142228.0e42abb0%40lakeview.
For more options, visit https://groups.google.com/d/optout.

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

[Viktor Ransmayr]

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 highlights of Leo 6.0
>
> Leo now requires python 3.6 or above.
> This greatly simplifies Leo's code.
> Leo's default gui uses Qt Docks.
> Use --no-dock to use Leo's legacy gui.
> Several commands now generate clickable links in the Log pane.
> This greatly speeds navigation.
> The usual assortment of bug fixes and minor improvements.

Installing Leo 6.0 beta 1 into a **new** virtual environment using pip
& PyPI is working as well.

Thanks a lot & I'll start investigating further now ...

With kind regards,

Viktor

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAAeSrG%2BDnD_4tCifick1TLqTtE6bZcVnVVrsp414_0%3D%3DFPOzvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use the bridge, Luke

[Edward K. Ream]

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 simply to be able to access Leo outline from either python
or vim script.  In python, all that is needed is access to c and g.  From
c, we get c.p and all the generators.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS1urRoCxmYZmoMw8A2qo7tWnEF3yWFBB-71YR0RBFwihQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use the bridge, Luke

[Terry Brown]

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 go?
> >
> > Not without much more specific objectives ;-)
> 
> The objective is simply to be able to access Leo outline from either
> python or vim script.  In python, all that is needed is access to c
> and g.  From c, we get c.p and all the generators.

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.  I
assume - I guess I can do something to verify that, but I can't see why
it wouldn't work.

Cheers -Terry

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/20190618182730.0cbb2997%40lakeview.
For more options, visit https://groups.google.com/d/optout.

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

[Viktor Ransmayr]

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 Wilkie: Is this serious enough to raise an issue?



(VE4Leo) PS C:\Users\Viktor\pyve\VE4Leo> pip show 
leo   Name: 
leo
Version: 6.0-devel
Summary: An IDE, PIM and Outliner
Home-page: http://leoeditor.com
Author: Edward K. Ream
Author-email: edream...@gmail.com
License: MIT License
Location: c:\users\viktor\pyve\ve4leo\lib\site-packages
Requires: nbformat, flexx, pyflakes, pylint, future, sphinx, six, PyQt5, 
docutils
Required-by:
(VE4Leo) PS C:\Users\Viktor\pyve\VE4Leo>  





(VE4Leo) PS C:\Users\Viktor\pyve\VE4Leo> pip install 
leo==6.0b1 
Collecting leo==6.0b1
  Downloading 
https://files.pythonhosted.org/packages/70/e5/3421fc20192f03c8378784f24dbbad3555966fdd4708b631023604cebe9d/leo-6.0b1-py2.py3-none-any.whl
 
(9.4MB)
 || 9.4MB 1.3MB/s
Requirement already satisfied: PyQt5; python_version >= "3.0" in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (5.11.3)
Requirement already satisfied: pyflakes in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (2.0.0)
Requirement already satisfied: docutils in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (0.14)
Requirement already satisfied: nbformat in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (4.4.0)
Requirement already satisfied: sphinx in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (1.8.3)
Requirement already satisfied: future in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (0.17.1)
Requirement already satisfied: pylint in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (2.2.2)
Requirement already satisfied: flexx; python_version >= "3.5" in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (0.8.0)
Collecting PyQtWebEngine (from leo==6.0b1)
  Downloading 
https://files.pythonhosted.org/packages/20/0f/d0d7b7e33bb3dc5411013886af43e8f922c2d8672d8173b6a5419e91ac56/PyQtWebEngine-5.12.1-5.12.3-cp35.cp36.cp37.cp38-none-win_amd64.whl
 
(49.0MB)
 || 49.0MB 595kB/s
Collecting meta (from leo==6.0b1)
  Downloading 
https://files.pythonhosted.org/packages/78/4e/bf6414dd628664eee7d03831f36fe9ffd43708c36c8bd43ae56ebe7cd69d/meta-1.0.2.tar.gz
 
(49kB)
 || 51kB 409kB/s
Requirement already satisfied: six in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from leo==6.0b1) (1.12.0)
Requirement already satisfied: PyQt5_sip<4.20,>=4.19.11 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from PyQt5; python_version 
>= "3.0"->leo==6.0b1) (4.19.13)
Requirement already satisfied: jupyter-core in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from nbformat->leo==6.0b1) 
(4.4.0)
Requirement already satisfied: jsonschema!=2.5.0,>=2.4 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from nbformat->leo==6.0b1) 
(2.6.0)
Requirement already satisfied: traitlets>=4.1 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from nbformat->leo==6.0b1) 
(4.3.2)
Requirement already satisfied: ipython-genutils in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from nbformat->leo==6.0b1) 
(0.2.0)
Requirement already satisfied: sphinxcontrib-websupport in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(1.1.0)
Requirement already satisfied: colorama>=0.3.5; sys_platform == "win32" in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(0.4.1)
Requirement already satisfied: requests>=2.0.0 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(2.21.0)
Requirement already satisfied: babel!=2.0,>=1.3 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(2.6.0)
Requirement already satisfied: snowballstemmer>=1.1 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(1.2.1)
Requirement already satisfied: alabaster<0.8,>=0.7 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(0.7.12)
Requirement already satisfied: imagesize in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(1.1.0)
Requirement already satisfied: packaging in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(18.0)
Requirement already satisfied: Jinja2>=2.3 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(2.10)
Requirement already satisfied: setuptools in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(39.0.1)
Requirement already satisfied: Pygments>=2.0 in 
c:\users\viktor\pyve\ve4leo\lib\site-packages (from sphinx->leo==6.0b1) 
(2.3.1)

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

[Edward K. Ream]

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
> environments I ran into trouble. - See attached logs.
>

> @Matt Wilkie: Is this serious enough to raise an issue?
>

As stated earlier this week, the answer to all such questions is "yes" :-)

Issues are the way all of us devs keep track of what needs attention.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS01QaGdT0RAX%2BQGanjntmXpe4PVP3eKwAQAY%3Dpm_HuYJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use the bridge, Luke

[Edward K. Ream]

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.  That would be helpful.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS1WoNrVgv%2BsdUTHz33aPot_mv%2B19GbYoPKGBCuyS9Ksfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.