Re: Matt, do you know why TravisCI isn't checking recent changes?

[Matt Wilkie]

I think there's more to it though. Thomas's PR is stuck in "waiting for 
status to be reported" mode, and I found a lot of similar threads. Sounds 
like a recurring GitHub <-> Travis integration problem. I've asked for help.

https://travis-ci.community/t/on-a-pr-some-checks-havent-completed-yet-waiting-for-status-to-be-reported/7951

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/6af31142-4708-4988-9d49-d578df222c03%40googlegroups.com.

Re: Matt, do you know why TravisCI isn't checking recent changes?

[Matt Wilkie]

>
> Take a look at https://github.com/leo-editor/leo-editor/branches/active.
>

umm, no. 

[Later] after some poking around discovered the [Requests] page.
https://travis-ci.org/github/leo-editor/leo-editor/requests
which says "GitHub payload is missing a merge commit (mergeable_state: 
"unknown", merged: false)" starting 4 hours ago and continuing for next 4 
commits.

I made a small commit to devel, which did trigger a new build, and that 
failed with "syntax error in: viewrendered2" (ref 
). 
Looks like a remaining merge marker:

Traceback (most recent call last):
>
>   File "/home/travis/build/leo-editor/leo-editor/leo/core/leoTest.py", line 
> 1364, in checkFileSyntax
>
> tree = compile(s + '\n', fileName, 'exec')
>
>   File "viewrendered3", line 945
>
> <<< HEAD
>
>  ^
>
> SyntaxError: invalid syntax
>
>
-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9ec47c44-73d5-46aa-8205-51306c9ed0c2%40googlegroups.com.

Re: About zoom vs leo-editor

[Matt Wilkie]

>
> Even better that Zoom is Jitsi[1], which doesn't do extensive data and 
> metadata collection just to have a simple conference, is open source, 
> gratis, multiplatform and just requires a link to start your talk.
>
> [1] meet.jit.si/
>

Thanks Offray. This is useful to me in another context (and maybe this one 
too ;-)
 

> Leo is awesome for a lot of other thinks.
>

Definately. The learning about other interesting things/thoughts feature of 
this group is what kept me here long enough to learn about Leo itself. ;-)

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ed9717bb-c7b6-4a9f-aed5-044a9705b1d0%40googlegroups.com.

Re: For Thomas: C++ problems in pyqt

[Thomas Passin]

According to your linked page, deleteLater() can lead to problems that give 
the very exception we are seeing. The places it shows up are in code that I 
inherited from VR/VR2, and just left in because I didn't really know why we 
needed it but supposed that someone before me had.

Most if not all cases relate to hiding the render pane.  So that gives me a 
place to look.  Why did someone think that the pane needs deleting after it 
is hidden?  Hmm...  Well, at least we always get a toolbar that behaves 
normally even after the error message. That's good!

On Wednesday, April 1, 2020 at 8:14:04 PM UTC-4, Thomas Passin wrote:
>
> Thanks, that looks like it could be relevant.
>
> On Wednesday, April 1, 2020 at 6:37:34 PM UTC-4, Edward K. Ream wrote:
>>
>> Here's the link. I found it while cleaning out my bookmarks :-)
>>
>> http://enki-editor.org/2014/08/23/Pyqt_mem_mgmt.html
>>
>> Maybe it will help find the memory problems in vr3.py.
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/6162cf5e-9f0e-4421-826e-1e6d65cd37ca%40googlegroups.com.

Re: Thomas, the fix branch fixes vr3.py

[Thomas Passin]

Edward, if you retrieved this file before about 9:30 PM Eastern, please get 
it again.  I found a bug where the line h = c.hash() in store_layout had 
been removed during my merge.  It needs to be there.

On Wednesday, April 1, 2020 at 8:00:27 PM UTC-4, Thomas Passin wrote:
>
> I merged the files.  For some reason I couldn't push my changes upstream  
> to the "fix" branch.  Although I was logged in to Github, it said it 
> couldn't authenticate.  So I pushed the changes to the devel branch of my 
> own fork and sent a PR.
>
> On Wednesday, April 1, 2020 at 6:31:35 PM UTC-4, Edward K. Ream wrote:
>>
>> Here is the checkin log for rev 69288fd in the fix branch:
>>
>> QQQ
>> Manually remove the git merge conflict markers as follows:
>> 
>> In *all* cases, removed everything between  and ===, using the second 
>> version.
>> 
>> Fixed one unmatched docstring delim.
>> 
>> Pylint reports that "h" is undefined in store_layout.
>> Neither version defined it.
>> QQQ
>>
>> Imo, this version is probably the best place for you to start. You are, 
>> however, free to use another base.
>>
>> I would like to merge fix into devel soon. Please let me know what you 
>> would like to do.
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/a1819e14-e5bb-446d-9ced-d3ee6002d1b3%40googlegroups.com.

Re: For Thomas: C++ problems in pyqt

[Thomas Passin]

Thanks, that looks like it could be relevant.

On Wednesday, April 1, 2020 at 6:37:34 PM UTC-4, Edward K. Ream wrote:
>
> Here's the link. I found it while cleaning out my bookmarks :-)
>
> http://enki-editor.org/2014/08/23/Pyqt_mem_mgmt.html
>
> Maybe it will help find the memory problems in vr3.py.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/8a82782c-003e-4902-b698-17dcfcd0fdc2%40googlegroups.com.

Re: Thomas, the fix branch fixes vr3.py

[Thomas Passin]

I merged the files.  For some reason I couldn't push my changes upstream  
to the "fix" branch.  Although I was logged in to Github, it said it 
couldn't authenticate.  So I pushed the changes to the devel branch of my 
own fork and sent a PR.

On Wednesday, April 1, 2020 at 6:31:35 PM UTC-4, Edward K. Ream wrote:
>
> Here is the checkin log for rev 69288fd in the fix branch:
>
> QQQ
> Manually remove the git merge conflict markers as follows:
> 
> In *all* cases, removed everything between  and ===, using the second 
> version.
> 
> Fixed one unmatched docstring delim.
> 
> Pylint reports that "h" is undefined in store_layout.
> Neither version defined it.
> QQQ
>
> Imo, this version is probably the best place for you to start. You are, 
> however, free to use another base.
>
> I would like to merge fix into devel soon. Please let me know what you 
> would like to do.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/fa3805ca-86ce-4d7d-ae74-d3ce0dabf690%40googlegroups.com.

Re: Jupyter vs Leo + VR3

[Offray Vladimir Luna Cárdenas]

It looks pretty cool in fact :-).

Thanks,

On 1/04/20 5:15 p. m., Thomas Passin wrote:
> Hi, I see you found us on another thread.  Here is a longer example. 
> It's a real one that I did for myself some time ago.  It is too long
> to show in a single image, so I exported it to the browser and printed
> to pdf. The page breaks aren't the best, but it was quick and simple. 
> It whets your appetite, doesn't it?
>
> Enjoy!
>
> On Wednesday, April 1, 2020 at 1:40:29 PM UTC-4, Offray Vladimir Luna
> Cárdenas wrote:
>
>
> I'm having problems these days running Leo on my Manjaro Linux.
> There is any screenshot to share about how Leo + vr3 plugin looks
> like, for example, in the context of scientific computing (lets
> say combining a calculation, an equation, some Markdown/ReST, and
> a plot?).
>
> -- 
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/d98fe616-a643-4bd5-9f78-d8e78c6f814b%40googlegroups.com
> .

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/aeb15a35-eb96-97b9-f1e4-30f4e91fd4cf%40riseup.net.

For Thomas: C++ problems in pyqt

[Edward K. Ream]

Here's the link. I found it while cleaning out my bookmarks :-)

http://enki-editor.org/2014/08/23/Pyqt_mem_mgmt.html

Maybe it will help find the memory problems in vr3.py.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/bc3da74a-efc5-4e40-97cb-10af726434a6%40googlegroups.com.

Matt, do you know why TravisCI isn't checking recent changes?

[Edward K. Ream]

Take a look at https://github.com/leo-editor/leo-editor/branches/active.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/127e90f9-9d9a-4df1-a1f8-3bf2fc6bdf25%40googlegroups.com.

Thomas, the fix branch fixes vr3.py

[Edward K. Ream]

Here is the checkin log for rev 69288fd in the fix branch:

QQQ
Manually remove the git merge conflict markers as follows:

In *all* cases, removed everything between  and ===, using the second 
version.

Fixed one unmatched docstring delim.

Pylint reports that "h" is undefined in store_layout.
Neither version defined it.
QQQ

Imo, this version is probably the best place for you to start. You are, 
however, free to use another base.

I would like to merge fix into devel soon. Please let me know what you 
would like to do.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/5d0083a8-db92-4798-a3d3-43e35074aca1%40googlegroups.com.

Re: What's next, continued

[Offray Vladimir Luna Cárdenas]

Hi,

Is good to see the path ahead and the upcoming focus.

On 23/03/20 8:11 a. m., Edward K. Ream wrote:
> 3. Imo, live coding is a dead end. The cool demos are toys which can
> not be scaled up:
>
> A: *Graphics*: Any graphics-based demo could be more easily recreated
> with a slider that changes the graphics values.
>
> Alternatively, you could just put your graphics code into a Leo node
> and hit Ctrl-B when you are ready for a new run.
>
> You could create an @button node to rerun the graphics code on every
> Leo keystroke, but that's just silly. Most of the time you would
> either get a syntax error or a graph using an intermediate value.
>
> B: *Music*.  Similarly, a "live" music app would be more usefully
> coded with sliders.
>
> C. *Apps*. Changing a large app on the fly is either silly, or
> dangerous, or both.
>
> I am not going to invest in learning the tools of the Pharo world.
> Otoh, browsing such tools lead me to Bokeh, so the time was well spent :-)

Live Coding has been a "dead end" full of "toys" for non-live coders
since about 40 years when file based editing, compiling, interpreting,
realoading programming style (Unix, C and friends) took over programmers
imagination and over live coding systems (Lisp Symbolic Machines and
Smalltalk Dynabook ones). Fortunately live coding is being alive and
kicking since its beginnings without the pressure of main stream
programming paradigms and languages.

Sliders could help here and there, but no amount of icons and sliders
will replace the power of symbolic programming. I would like to see
sliders based code editing for Leo sources, and just being able to
express code manipulation that someone already pre-programed in a slider
as a replace of direct textual manipulation. I can't imagine how
software as a graph[1], (Python powered) music[2][2a] or the idea of
programming as performance[3] can be expressed only via sliders and I
can't imagine neither any creative endeavors advised to not do changes
on the fly because of the previous conception of live coding (for
example don't do your live coding is Jupyter, it's just a toy that can
be scaled up or don't do data manipulation on the fly because of the
silliness and danger of such approach).

[1] https://vimeo.com/94724841
[2] https://www.youtube.com/watch?v=xXNB1BbKY8A
[2a] https://foxdot.org/
[3] https://www.youtube.com/watch?v=0lTZ8Tuyu5I

Of course different readings of diverse tech ecosystems are important
and anyone can choose to explore (or not) some particular stack(s). In
my case, as a non-professional coder, as live coding and moldability
became more and more important I saw that Python was not the path to
follow, but that path (which has its value despite not being the one I
would stay) let me to Leo and this community and after that to Pharo,
Roassal, etc. So despite not being an active user of Python or Leo,
because they don't provide the live coding + moldability I want/need, it
has been time well spent/invested and still is to be around in this
community.

Cheers,

Offray

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/fbdeab87-05be-7b6e-21da-a626b112b2e4%40riseup.net.

Re: About VR3, holoviews and bokeh

[Offray Vladimir Luna Cárdenas]

This looks really cool! I was asking for a inspiring screenshot in other
thread, unknowing that I would find them here.

Thanks a lot,

Offray

On 30/03/20 7:34 a. m., Thomas Passin wrote:
> And it turns out that it's just as easy to work with Seaborn,
>
> On Monday, March 30, 2020 at 6:48:29 AM UTC-4, Edward K. Ream wrote:
>
> Thomas Passin and I have been discussing his vr3 plugin in
> private. This is a great plugin. Our conversation deserves to be
> public.
>
> Here I am going to discuss what I think I know about vr3 and its
> relationship with the holoviews and bokeh
> packages. 
> I'll keep this as short as possible.
> [snip]
>
> -- 
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/b3d7a8a2-2d53-4b8e-ac47-a09539dacc0a%40googlegroups.com
> .

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/4c262b5d-d8ce-f310-983e-9f423448a963%40riseup.net.

Re: Jupyter vs Leo + VR3

[Offray Vladimir Luna Cárdenas]

Hi,

Nice to see this theme become alive again, as Jupyter interactive alike
experiences combining with Leo outiling alike experience have been
discussed before. We could have interactive emergent computing. I have
been a log advocate of them and it was the reason I prototyped
Grafoscopio[1], after long trying to get such experience using Python
based technologies and dealing with a lot of incidental complexity.

[1] https://mutabit.com/grafoscopio/en.html

At some point I suggested Leo interacting with Jupyter and other
projects not by importing and exporting files from/to them, but by
establishing bridges (similar to Pyzo, AFAIK) that let Leo talk with
such programs and import results as "@output" cells/nodes. Maybe the vr3
is the missing piece that would allow such interactive outlining computing.

I'm having problems these days running Leo on my Manjaro Linux. There is
any screenshot to share about how Leo + vr3 plugin looks like, for
example, in the context of scientific computing (lets say combining a
calculation, an equation, some Markdown/ReST, and a plot?).

Cheers,

Offray

On 31/03/20 6:24 a. m., Edward K. Ream wrote:
> Thomas, this post is an indirect response to some of your recent
> remarks. There is some chance I understand them now ;-)
>
> When I awoke this morning I saw that Leo + vr3 looks to be /superior
> /to Jupyter! vr3 adds all essential features of Jupyter notebooks and
> cells, while retaining Leo's unique features:
>
> 1. Interleaved @language directives is /way /better than the clumsy
> dropdown menu in Jupyter that selects the default view.
>
> 2. vr3 is aware of outline structure.
>
> 3. Leo + vr3 naturally retains all of Leo's superior organizational
> abilities.
>
> 4. In the (unlikely?) event that people want to use both Leo and
> jupyter, Leo can already import/export with jupyter.
>
> *No jupyter bridge needed*
>
> This page
> 
> discusses using bokeh with jupyter. I'm not sure what this page is
> getting at, but the page appears moot.
>
> I had been thinking of resuscitating #1386
> , but that issue
> looks like it can remain a "Won'tDo".
>
> *Summary*
>
> Thomas's vr3 plugin makes every Leo node work like an /enhanced/
> jupyter cell.
>
> All comments welcome.
>
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/7d2b9eac-6baa-4cb3-b22c-e1a22163219b%40googlegroups.com
> .

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c1cd7592-9e64-2778-afdc-6151957dbb96%40riseup.net.

Re: About zoom vs leo-editor

[Offray Vladimir Luna Cárdenas]

Hi,

Even better that Zoom is Jitsi[1], which doesn't do extensive data and
metadata collection just to have a simple conference, is open source,
gratis, multiplatform and just requires a link to start your talk.

[1] meet.jit.si/

Leo is awesome for a lot of other thinks.

Cheers,

Offray

On 31/03/20 6:01 a. m., Edward K. Ream wrote:
> When I awoke this morning I saw that our text communications in
> leo-editor have significant advantages over zoom conversations: they
> are public and permanent. We can read and reread postings at our leisure.
>
> I have been overestimating the value of face-to-face discussions based
> on a paper (probably in Nature or Science) that stated that physical
> proximity of collaborators improved their creativity/innovation. That
> conclusion /might/ still be true, but that paper was written a long
> time ago by internet standards.
>
> *Summary*
>
> zoom is great for getting acquainted. I'll be happy to set up a zoom
> time with any of you.
>
> Imo, the leo-editor forum is significantly better than zoom for
> engineering discussions.
>
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/58f510bc-e613-46de-9a98-4221b872b05d%40googlegroups.com
> .

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/aafd2a1a-bcae-2a10-7ccb-ad91b632676f%40riseup.net.

Re: warning viewrender3.py plugin has been commited with unresolved conflicts.

[Thomas Passin]

Right, and Edward has already asked me to clear this up.

On Wednesday, April 1, 2020 at 11:38:11 AM UTC-4, vitalije wrote:
>
> Title tells everything. While executing unit tests, two are failing: check 
> syntax of all files and pluginTestCase for viewrender3.
>
> Vitalije
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/616eaf41-3636-42d2-95b3-3c28fc7e057e%40googlegroups.com.

warning viewrender3.py plugin has been commited with unresolved conflicts.

[vitalije]

Title tells everything. While executing unit tests, two are failing: check 
syntax of all files and pluginTestCase for viewrender3.

Vitalije

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/e601db11-257d-4e10-9c97-f95ef2e7466d%40googlegroups.com.

Re: FYI: pylint-leo-rc-ref.txt disables two new pylint tests

[Edward K. Ream]

On Wed, Apr 1, 2020 at 9:45 AM Thomas Passin  wrote:

> It's really a comprehension vs brevity thing, and a matter of personal
> style.
>

No. It's a pylint bug. Enable the two checks and look at the warnings.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS19VbUR726-a86N6JZQ_5HoMMnixAsW0rWv5WvZtKaq1g%40mail.gmail.com.

Re: About zoom vs leo-editor

[Matt Wilkie]

>
> ...I can certainly imagine using Leo to grab and re-arrange snippets from 
>> lectures and so on.
>>
>
> Excellent ideas. Please create an enhancement request.
>

Done! https://github.com/leo-editor/leo-editor/issues/1556

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ba1cf834-1413-43d2-b6f4-5b9ff5d848fc%40googlegroups.com.

Re: FYI: pylint-leo-rc-ref.txt disables two new pylint tests

[Thomas Passin]

It's really a comprehension vs brevity thing, and a matter of personal 
style.  Removing the else gives shorter code, which is *usually* more 
clear.  But without the *else*, you have to *infer* its virtual presence, 
and that interferes with comprehension.  I'm not consistent about this, 
myself.  But functionally, sure, both forms are the same.

On Wednesday, April 1, 2020 at 9:52:27 AM UTC-4, vitalije wrote:
>
> I doubt that. A few days ago I've run pylint and it reported some 
> complains about non necessary else after break, or after return. My first 
> reaction was just like yours, but then I looked more closely and those 
> complains were correct.
>
> while True:
> ... # some code here
> if condition:
>  break
> else:
>  do_something_else_here()
>
> # or 
> def f():
> # some code ...
> if condition:
> return result_a
> else:
> do_other_thing()
> # ... 
> return result_b
>
>
>  In both cases, meaning of the program is the same as if the else block 
> was unindented and else removed.
>
> Vitalije
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/2b0a9209-30fc-413a-be35-a152c30ebdd1%40googlegroups.com.

Re: FYI: pylint-leo-rc-ref.txt disables two new pylint tests

[Edward K. Ream]

On Wed, Apr 1, 2020 at 8:52 AM vitalije  wrote:

> I doubt that. A few days ago I've run pylint and it reported some
> complains about non necessary else after break, or after return. My first
> reaction was just like yours, but then I looked more closely and those
> complains were correct.
>
> while True:
> ... # some code here
> if condition:
>  break
> else:
>  do_something_else_here()
>
> # or
> def f():
> # some code ...
> if condition:
> return result_a
> else:
> do_other_thing()
> # ...
> return result_b
>
>
>  In both cases, meaning of the program is the same as if the else block
> was unindented and else removed.
>

The test is valid in the cases you give. However, the test is invalid if
the break is within an 'if' statement. It's a botch.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2%3DrRVRL_8EqMonvj%3DC3GQUDONG%3DaT8TOek2qghUMBg9w%40mail.gmail.com.

Re: FYI: pylint-leo-rc-ref.txt disables two new pylint tests

[vitalije]

I doubt that. A few days ago I've run pylint and it reported some complains 
about non necessary else after break, or after return. My first reaction 
was just like yours, but then I looked more closely and those complains 
were correct.

while True:
... # some code here
if condition:
 break
else:
 do_something_else_here()

# or 
def f():
# some code ...
if condition:
return result_a
else:
do_other_thing()
# ... 
return result_b


 In both cases, meaning of the program is the same as if the else block was 
unindented and else removed.

Vitalije

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/74c88487-6eb9-40a7-a38d-41b12714e770%40googlegroups.com.

FYI: pylint-leo-rc-ref.txt disables two new pylint tests

[Edward K. Ream]

leo/test/pylint-leo-rc-ref.txt now disables the following two new tests:

no-elif-break
no-else-break

Imo, these are just plain wrong. Following the pylint advice would change 
the meaning of the program. These look like serious pylint bugs.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/557cae26-0395-4e04-b161-67caea312d9d%40googlegroups.com.

Re: Tom, please fix vr3 in devel

[Edward K. Ream]

On Wednesday, April 1, 2020 at 8:05:28 AM UTC-5, Thomas Passin wrote:
>
> OK, I'll take a run at it.  It can be difficult when you have a lot of 
> changes that are mostly whitespace and style.
>

Just make sure there are no merge markers like <<, == and >>. 
Somebody can beautify the code later :-)

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/4c77cf4c-9180-4c8c-988c-788f09ce1936%40googlegroups.com.

Re: Tom, please fix vr3 in devel

[Thomas Passin]

OK, I'll take a run at it.  It can be difficult when you have a lot of 
changes that are mostly whitespace and style.  I messed one up that way 
recently, too.

On Wednesday, April 1, 2020 at 6:34:20 AM UTC-4, Edward K. Ream wrote:
>
> Somehow it contains many conflict markers from a git merge.
>
> Not sure how this happened. Presumably the PR went awry.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c868c836-34be-4940-a43f-df9194f2a837%40googlegroups.com.

Re: Tom, please fix vr3 in devel

[Thomas Passin]

It's always annoying when there are a lot of whitespace and style changes.  
I'll see about it.

(For the benefit of anyone else who is wondering what this is about, this 
commit  tried to remove a lot of complaints from pylint about whitespace 
and other sylistic nits that had build up over the years.  It was totally 
non-functional).

On Wednesday, April 1, 2020 at 6:34:20 AM UTC-4, Edward K. Ream wrote:
>
> Somehow it contains many conflict markers from a git merge.
>
> Not sure how this happened. Presumably the PR went awry.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/40b098b2-d967-47f7-a832-ed56a0341fe8%40googlegroups.com.

Re: Tom, please fix vr3 in devel

[Edward K. Ream]

On Wednesday, April 1, 2020 at 5:34:20 AM UTC-5, Edward K. Ream wrote:
>
> Somehow it contains many conflict markers from a git merge.
>

It should be easy for you. From a branch that contains your desired vr3.py:

- git merge devel (Will likely create a merge conflict).
- git checkout --ours leo\plugins\viewrendered3.py
- git add .
- git checkout devel
- git merge 
- git push

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/074ac984-8ea5-441c-a0b4-ec948604da9e%40googlegroups.com.

Tom, please fix vr3 in devel

[Edward K. Ream]

Somehow it contains many conflict markers from a git merge.

Not sure how this happened. Presumably the PR went awry.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/6f502b37-d5d1-48b5-a735-e28d57e023d2%40googlegroups.com.

Re: Leo and Jupyter

[Edward K. Ream]

On Tue, Mar 31, 2020 at 1:03 PM Thomas Passin  wrote:

I don't see the point of working with Jupyter/ipython in Leo unless we can
> actually make use of Leo's strengths.
>

I agree.

Last year we reached consensus that embedding Leo into emacs or vim is a
bad idea. Similar logic applies here.

Otherwise, Jupyter notebooks are very good, highly developed, and have many
> features (like their kernels for other languages and widgets) that we will
> never be able to duplicate in Leo.  Leo is especially good at at
> navigation, viewing, and and modification of the outline, and I don't want
> to give that up.
>

Yes.

You and I have been discussing vr3 architecture privately recently. Let's
make sure future discussions are here on leo-editor. vr3 looks to be just
what is needed.

The whole point of thinking about getting Leo to play with Jupyter would be
> to be potentially share notebooks with Jupyter users.
>

I agree.

> Otherwise, we can just make Leo notebooks using VR3 or some similar plugin
> - I think I'd be happy with that - and we get all the advantages of Leo and
> the notebook-style approach.  And it would be a lot easier in terms of
> development effort.
>

Imo, vr3 will offer very substantial advantages over jupyter. So now people
will have a happy choice: use Jupyter or Leo, whichever best suits their
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0x0W%3DuNQyTJHm0SVh0v4uXUxMMXd6Ny4vdEhBj6c9gNw%40mail.gmail.com.

Re: Leo and Jupyter

[Edward K. Ream]

On Tue, Mar 31, 2020 at 10:44 AM 'tfer' via leo-editor <
leo-editor@googlegroups.com> wrote:

> There is another option we could consider, rather than full juypter stuff,
> just add an Ipython console tab to the log pane.  Though not as sexy as
> Juypter, it has most of its guts, is embed-able, and has a qt-console
> version.
>

Iirc, doing this is non-trivial, for reasons that I don't remember ;-)

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2Pw-Zip26MapidkBzMO%3DDnxBG1PVQ7R6nk8aHga6xSqg%40mail.gmail.com.

Re: About zoom vs leo-editor

[Edward K. Ream]

On Tue, Mar 31, 2020 at 7:35 PM Matt Wilkie  wrote:

> Imagine Leo turned to this task, headlines would label snippets of audio
>> captured in their body
>
>
> I started a course today called Introduction to Mathematical Thinking
> .
> One of the things this offering has that beats the pants off other video
> courses I've been subjected to is that it has a full text transcript, and
> they are tied together. Skip ahead in the video and so does the transcript.
> Click on a sentence in the transcript and it jumps to that part of the
> video. I would love to have this in podcasts and especially audio books.
>
> ...I can certainly imagine using Leo to grab and re-arrange snippets from
> lectures and so on.
>

Excellent ideas. Please create an enhancement request.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2gkMkGmyALsEuAyiOdYc-QteqfUaxV6-vSXU9zyF0b7w%40mail.gmail.com.

Re: About zoom vs leo-editor

[Edward K. Ream]

On Tue, Mar 31, 2020 at 12:52 PM 'tfer' via leo-editor <
leo-editor@googlegroups.com> wrote:

> Just like the outliner "More" provided inspiration for Leo, Leo provides
> me with inspiration for various thinking, capturing, organizing tools.
> I've mentioned my idea for a presentation plugin for reveal.js, here's
> another.
>
> Now that solid state memory has freed us from from the micro-cassettes of
> yore, I'm amazed of how little innovation there has been in voice recorder
> apps.  Something that allows for more than labeling a big block of
> narration is needed.
>
> Imagine Leo turned to this task, headlines would label snippets of audio
> captured in their body.  To give a visual representation of the ongoing
> capture, generate a sequence of dashes to represent words, (not exact, more
> to hint and show duration).  You could add to this by adding punctuation
> via the keyboard while dictating.  Headlines can typed in and the snippets
> rearranged/split/combined.  Speech to text can be applied, (more to sharpen
> the visual representation then to provide text, STT is still pretty iffy --
> but it could do a better job at providing dashes for words, maybe add an
> initial an final letter to some.  The text would be available in another
> pane, a "pacer" would follow along with playback.
>
> The biggest thing this all provides is a way to capture
> thoughts/conversations and a way to access them in a non-linear way.
>

Thanks for these ideas. I suggest creating an enhancement issue. Otherwise
they will be forgotten.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS1RFBvjP72n10i-niGad2tBmRiDowPxu6h8LkcuyvE50g%40mail.gmail.com.

Re: Jupyter vs Leo + VR3

[Edward K. Ream]

On Tue, Mar 31, 2020 at 8:00 PM Thomas Passin  wrote:

>
> On Tuesday, March 31, 2020 at 6:42:01 PM UTC-4, Edward K. Ream wrote:
>
>> As you say, at present the ipynb.do_cell method (in importers/ipynb.py)
>> doesn't save much. It should be easy to save more, if you would like that.
>>
>
> Easy, perhaps, but I would go slowly, because we need to look at how best
> to fit it into VR3-style node trees, and also to see if we can have a hope
> of round-tripping with good fidelity.
>

I agree.

> Of course, I have only a general idea of how the notebook structure works,
> and I'm sure you are way ahead of me there.
>

Almost all you need to know is that .ipynb files are json. And that's about
all I remember.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS3Qs2Mb_%2BBT87LKTYNFSYggOoCuZHFkMxmuwWUmtCx7bg%40mail.gmail.com.