Re: I Love Leo :)

[Satish Goda]

Thank you for the welcome folks.

Offray, I will take a look at the links. Thank you!

- Satish.

On Wednesday, December 14, 2016 at 11:24:59 PM UTC+8, Offray Vladimir Luna 
Cárdenas wrote:
>
> Hi,
>
> Welcome. Leo is a powerful and inspiring tool and I hope you continue to 
> enjoy it. I certainly do.
>
> I see by your tweets that you're making explorations on how to use Leo for 
> documentation and storytelling, creating custom interface for your needs. I 
> started "hacking" Leo by making some @buttons to customize it for my 
> research writing. I fact reading your tweets I was able to find some of 
> mine that document such process. Five years ago I made my first tweet about 
> Leo Editor (the etherpad is now lost) [1]. And 3 years ago I started to use 
> #LeoEditor hashtag[2] to talk about how to mix ideas of Leo and IPython. 
> They finally did, but in a Pharo/Smalltalk live coding environment[3][4][5]
> [1] https://twitter.com/offrayLC/status/134323911625162752
> [2] https://twitter.com/offrayLC/status/309113951646523392
> [3] 
> http://mutabit.com/offray/static/blog/output/posts/on-deepness-and-complexity-of-ipython-documents.html
> [4] 
> http://mutabit.com/offray/static/blog/output/posts/grafoscopio-idea-and-initial-progress.html
>  
> 
> [5] http://mutabit.com/grafoscopio/index.en.html 
> 
>
> I still use Leo for note keeping and bookmarking. I found it pretty 
> ergonomic in the shortcuts and even now that I'm more into in interactive 
> documentation and live coding, the community and tool are a good source of 
> food for thought and a place to follow/have interesting talks.
>
> Welcome again!
>
> Offray
>
>
>
> On 14/12/16 04:12, Satish Goda wrote:
>
> Hello Folks.
>
> I came across Leo recently and I am hooked to it. Thank you to Edward and 
> the community for creating/maintaining/improving such a wonderful piece of 
> software tool.
>
> I have been promoting Leo on Twitter via the hashtag #leoeditor.
>
> https://twitter.com/hashtag/leoeditor?f=tweets=default
>
> Thank you.
>
> Satish Goda.
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to leo-e...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/leo-editor.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: leo stalling for long periods

['Terry Brown' via leo-editor]

Looking around a bit more, looks like you can disable those file checks with
@bool check_for_changed_external_files = False

in @settings, I see I have that set to False on the machine where the 
checkswere causing trouble for me, try that and see if it helps.
Cheers -Terry

 
  From: Curtis Carlsen 
 To: leo-editor  
 Sent: Wednesday, December 14, 2016 1:32 PM
 Subject: Re: leo stalling for long periods
   
The file consists of hundreds of smaller nodes.  There may be a few large 
nodes, but I find the warning screen about the QT lost data bug annoying so I 
usually delete them.

The original file is my work diary, built up over many months.  It has lots of 
proprietary company data.  The boss would not be pleased with me sharing it.

I usually close out the diary files after about a year, because they get slow 
to work with.  But the symptoms this time are different.  Everything is running 
along fast and then just stops.  It kinda has the feel of a thread getting 
stalled by a locked resource.  I seem to recall some kind of issue with python 
getting locked up on multiprocessors because of a poorly designed global lock, 
I have no idea if that could actually be involved, but it's just something I 
remember.

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: leo stalling for long periods

['Terry Brown' via leo-editor]

If the nodes are small and it worked before, it's probably not size related - I 
was thinking of syntax highlighting, but that's probably not it.
Are any of the files you're working with non-local, i.e. on network file 
systems?  I've had trouble with that, and I think Leo started scanning loaded 
files for external changes recently.  Seems like that's a possibility.
You can set the threshold for seeing the QT lost data bug (bytes in a single 
node), if you don't think the bugs impacting you and you're seeing the warning 
too often.
If you're familiar with git, you could try running git bisect to find the exact 
commit that broke things.
Re Python and threads, Pyhton's GIL Global Interpreter Lock prevents more than 
one *thread* using CPU time at once.  But Leo's limited use of threading hasn't 
changed recently, that I know of... although on-idle handling did change not 
that long ago. 
 
  From: Curtis Carlsen 
 To: leo-editor  
 Sent: Wednesday, December 14, 2016 1:32 PM
 Subject: Re: leo stalling for long periods
   
The file consists of hundreds of smaller nodes.  There may be a few large 
nodes, but I find the warning screen about the QT lost data bug annoying so I 
usually delete them.

The original file is my work diary, built up over many months.  It has lots of 
proprietary company data.  The boss would not be pleased with me sharing it.

I usually close out the diary files after about a year, because they get slow 
to work with.  But the symptoms this time are different.  Everything is running 
along fast and then just stops.  It kinda has the feel of a thread getting 
stalled by a locked resource.  I seem to recall some kind of issue with python 
getting locked up on multiprocessors because of a poorly designed global lock, 
I have no idea if that could actually be involved, but it's just something I 
remember.

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: leo stalling for long periods

[Curtis Carlsen]

The file consists of hundreds of smaller nodes.  There may be a few large 
nodes, but I find the warning screen about the QT lost data bug annoying so 
I usually delete them.

The original file is my work diary, built up over many months.  It has lots 
of proprietary company data.  The boss would not be pleased with me sharing 
it.

I usually close out the diary files after about a year, because they get 
slow to work with.  But the symptoms this time are different.  Everything 
is running along fast and then just stops.  It kinda has the feel of a 
thread getting stalled by a locked resource.  I seem to recall some kind of 
issue with python getting locked up on multiprocessors because of a poorly 
designed global lock, I have no idea if that could actually be involved, 
but it's just something I remember.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: I Love Leo :)

[Offray Vladimir Luna Cárdenas]

Hi,

Welcome. Leo is a powerful and inspiring tool and I hope you continue to 
enjoy it. I certainly do.


I see by your tweets that you're making explorations on how to use Leo 
for documentation and storytelling, creating custom interface for your 
needs. I started "hacking" Leo by making some @buttons to customize it 
for my research writing. I fact reading your tweets I was able to find 
some of mine that document such process. Five years ago I made my first 
tweet about Leo Editor (the etherpad is now lost) [1]. And 3 years ago I 
started to use #LeoEditor hashtag[2] to talk about how to mix ideas of 
Leo and IPython. They finally did, but in a Pharo/Smalltalk live coding 
environment[3][4][5]


[1] https://twitter.com/offrayLC/status/134323911625162752
[2] https://twitter.com/offrayLC/status/309113951646523392
[3] 
http://mutabit.com/offray/static/blog/output/posts/on-deepness-and-complexity-of-ipython-documents.html
[4] 
http://mutabit.com/offray/static/blog/output/posts/grafoscopio-idea-and-initial-progress.html

[5] http://mutabit.com/grafoscopio/index.en.html

I still use Leo for note keeping and bookmarking. I found it pretty 
ergonomic in the shortcuts and even now that I'm more into in 
interactive documentation and live coding, the community and tool are a 
good source of food for thought and a place to follow/have interesting 
talks.


Welcome again!

Offray



On 14/12/16 04:12, Satish Goda wrote:

Hello Folks.

I came across Leo recently and I am hooked to it. Thank you to Edward 
and the community for creating/maintaining/improving such a wonderful 
piece of software tool.


I have been promoting Leo on Twitter via the hashtag #leoeditor.

https://twitter.com/hashtag/leoeditor?f=tweets=default

Thank you.

Satish Goda.
--
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: I Love Leo :)

[Jacob Peck]

Welcome to the fold!

:)

-->Jake

On 12/14/2016 4:12 AM, Satish Goda wrote:

Hello Folks.

I came across Leo recently and I am hooked to it. Thank you to Edward 
and the community for creating/maintaining/improving such a wonderful 
piece of software tool.


I have been promoting Leo on Twitter via the hashtag #leoeditor.

https://twitter.com/hashtag/leoeditor?f=tweets=default

Thank you.

Satish Goda.
--
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.
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.
For more options, visit https://groups.google.com/d/optout.