Re: New plugin history_tracer

2019-09-30 Thread vitalije
Here is the Windows10 version: leo-ver-serv-v0.1.7.exe 
 sha1:  
0d79fd1864d31f190ed3b33e708778ebc4fd8ee6

This morning I've successfully built it with the `cargo install 
leo-ver-serv` command on Windows10 laptop.

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/11420f1f-36a8-44c0-9d32-84ffae1182bb%40googlegroups.com.


leo from devel fail to start on windows

2019-09-30 Thread gar
python launchLeo.py --no-dock

--global-docks: False

duplicate, (not conflicting) key bindings in myLeoSettings.leo
  tree Tab focus-to-body
   all Tab indent-region
  text Tab newline-and-indent
Leo 6.1-devel, devel branch, build 4e9d54b82e
2019-09-30 17:09:04 -0500
leo_excepthook Uncaught Python exception: [WinError 3] The system cannot 
find the path specified: 
'D:/bin/chocolatey/lib/python3/tools/lib/site-packages/leo/scripts/scripts.leo'

NoneType: None


E:\git\leo-editor>python --version
Python 3.7.4


CLI args are sufficient.
This can definitely be caused by python version upgrade (seems like that 
path points to old python's path) - but got no idea how.
Leo installed with PIP works fine.
Version from git launched ok before I pulled the changes.

-- 
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/6ea068e0-1e25-4192-b546-5cf4ceb4b479%40googlegroups.com.


Re: New plugin history_tracer

2019-09-30 Thread Chris George
It installed flawlessly on Linux.

Chris

On Mon, Sep 30, 2019 at 4:29 PM vitalije  wrote:

> I am travelling and can't do much about this at the moment. From the log I
> see that it complains about missing text test files. They aren't essential.
> Try adding any text files on those paths. They only serve for testing and I
> should have added them to the repository, but I had forgotten. When I get
> back I'll add them to git.
>
> Vitalije
>
> On Tuesday, October 1, 2019 at 12:06:27 AM UTC+2, Edward K. Ream wrote:
>>
>>
>>
>> On Sat, Sep 28, 2019 at 1:22 PM vitalije  wrote:
>>
>>> I finally got around to pack and publish my new plugin history_tracer.
>>>
>> ...
>>
>>> If you have cargo installed then installation of leo-ver-serv would be
>>> quite easy.
>>> cargo install leo-ver-serv
>>>
>>
>> On windows I get this:
>>
>> Updating crates.io index
>>   Installing leo-ver-serv v0.1.7
>> error: failed to compile `leo-ver-serv v0.1.7`, intermediate artifacts
>> can be found at `C:\Users\EDREAM~1\AppData\Local\Temp\cargo-installzk33CR`
>>
>> Caused by:
>>   failed to download `fossil-delta v0.1.6`
>>
>> Caused by:
>>   unable to get packages from source
>>
>> Caused by:
>>   failed to unpack package `fossil-delta v0.1.6`
>>
>> Caused by:
>>   failed to unpack entry at `fossil-delta-0.1.6/src/test-data/file-b.txt`
>>
>> Caused by:
>>   failed to unpack
>> `C:\Users\edreamleo\.cargo\registry\src\github.com-1ecc6299db9ec823\fossil-delta-0.1.6\src\test-data\file-b.txt`
>>
>> 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/1a375568-4aec-4cad-bf0d-6178a3e46165%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/CADWQas25h4syk53GbDY_hq06xfmK9E%3DrtVyOLVsQVq%2B3EV44ww%40mail.gmail.com.


Re: New plugin history_tracer

2019-09-30 Thread vitalije
I am travelling and can't do much about this at the moment. From the log I 
see that it complains about missing text test files. They aren't essential. 
Try adding any text files on those paths. They only serve for testing and I 
should have added them to the repository, but I had forgotten. When I get 
back I'll add them to git. 

Vitalije

On Tuesday, October 1, 2019 at 12:06:27 AM UTC+2, Edward K. Ream wrote:
>
>
>
> On Sat, Sep 28, 2019 at 1:22 PM vitalije > 
> wrote:
>
>> I finally got around to pack and publish my new plugin history_tracer.
>>
> ... 
>
>> If you have cargo installed then installation of leo-ver-serv would be 
>> quite easy.
>> cargo install leo-ver-serv
>>
>
> On windows I get this:
>
> Updating crates.io index
>   Installing leo-ver-serv v0.1.7
> error: failed to compile `leo-ver-serv v0.1.7`, intermediate artifacts can 
> be found at `C:\Users\EDREAM~1\AppData\Local\Temp\cargo-installzk33CR`
>
> Caused by:
>   failed to download `fossil-delta v0.1.6`
>
> Caused by:
>   unable to get packages from source
>
> Caused by:
>   failed to unpack package `fossil-delta v0.1.6`
>
> Caused by:
>   failed to unpack entry at `fossil-delta-0.1.6/src/test-data/file-b.txt`
>
> Caused by:
>   failed to unpack 
> `C:\Users\edreamleo\.cargo\registry\src\github.com-1ecc6299db9ec823\fossil-delta-0.1.6\src\test-data\file-b.txt`
>
> 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/1a375568-4aec-4cad-bf0d-6178a3e46165%40googlegroups.com.


Re: leo_in_pyzo plugin is ready for testing

2019-09-30 Thread lewis
I'm sure you meant *pyzo_in_leo* plugin :)

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/3fef75c9-0d78-432a-986e-478fd977705e%40googlegroups.com.


Re: New plugin history_tracer

2019-09-30 Thread Edward K. Ream
On Sat, Sep 28, 2019 at 1:22 PM vitalije  wrote:

> I finally got around to pack and publish my new plugin history_tracer.
>
...

> If you have cargo installed then installation of leo-ver-serv would be
> quite easy.
> cargo install leo-ver-serv
>

On windows I get this:

Updating crates.io index
  Installing leo-ver-serv v0.1.7
error: failed to compile `leo-ver-serv v0.1.7`, intermediate artifacts can
be found at `C:\Users\EDREAM~1\AppData\Local\Temp\cargo-installzk33CR`

Caused by:
  failed to download `fossil-delta v0.1.6`

Caused by:
  unable to get packages from source

Caused by:
  failed to unpack package `fossil-delta v0.1.6`

Caused by:
  failed to unpack entry at `fossil-delta-0.1.6/src/test-data/file-b.txt`

Caused by:
  failed to unpack
`C:\Users\edreamleo\.cargo\registry\src\github.com-1ecc6299db9ec823\fossil-delta-0.1.6\src\test-data\file-b.txt`

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/CAMF8tS1Gy4iJvQNN88tC-95BrtevXCKZZW-yerRW3nSvr7W%2Bdg%40mail.gmail.com.


Re: How to trace Leo Core?

2019-09-30 Thread Edward K. Ream
On Sun, Sep 29, 2019 at 3:59 PM Brian Theado  wrote:

> I've discovered https://github.com/ionelmc/python-hunter and it is
> excellent. You can filter exactly which modules do and don't get traced and
> the colorized output looks nice.
>

Thanks for this link.  I've bookmarked it.

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/CAMF8tS2tQWwJWXytvXOqoyb4_Hum%2Bwv9CU8%2B8d3-Fu5Ofmqw1g%40mail.gmail.com.


Re: How to trace Leo Core?

2019-09-30 Thread Edward K. Ream
On Sun, Sep 29, 2019 at 2:43 PM Viktor Ransmayr 
wrote:

>
> I tried to find out, if I can enable 'auditing/ tracing' for Leo in order
> to 'visualize' the run-time behavior of Leo Core ...
>

The various --trace options are good if they tell you what you want to see.

Usually, I put g.trace statements into Leo's source code.  A cff shows
there are 414 nodes in Leo's code with such statements, so you shouldn't
have too much trouble finding examples :-)

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/CAMF8tS04WpTkhNO6B3G1CCJ%3DVvdqFcsjyzATD3V%2Bz1XGRiKXFw%40mail.gmail.com.


Re: For devs: the new "delegated" label

2019-09-30 Thread Edward K. Ream
On Sun, Sep 29, 2019 at 9:51 AM vitalije  wrote:

> I am not very convinced that is the case. I think they sometimes are put
just because you or any other developer thought they might be useful.

In this case there was a specific request from a user.

> I remember that I have tried two or more times in the past to fix this
issue. I don't remember very well the details but I do remember that I
bumped every time in the roadblock which required some very ugly hacks.

I'll look into this. We are past the point were additional explanations
would be useful.

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/CAMF8tS1ju_%2BX%2BMqc0n%2B_FjZkaqu2D3k5QcmWrzhU_KmvmK8sKg%40mail.gmail.com.


leo_in_pyzo plugin is ready for testing

2019-09-30 Thread Edward K. Ream
The code is in devel.  Most of #1093 
 is complete. This is 
a major milestone in the plugin's history.

--global-docks must be in effect to use this plugin.

*Status*

- Leo fully inits pyzo, and creates a Pyzo menu in each opened Leo outline.
- All known gui-related glitches have been fixed.
- Pyzo knows nothing of Leo. At present Leo knows only a little about pyzo.

*To do*

- Leo should remember which files pyzo has open, and possibly other 
pyzo-related settings.
- Add Leo commands to access pyzo features.

*Summary*

Many features remain untested.  Please let me know your experiences.

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/82ce606d-dcab-41b5-8ffa-116738d180c3%40googlegroups.com.


Re: How to trace Leo Core?

2019-09-30 Thread Viktor Ransmayr
Hello Brian,

Am So., 29. Sept. 2019 um 22:59 Uhr schrieb Brian Theado <
brian.the...@gmail.com>:

> Edward can speak to the built-in leo traces, but there are also other
> options.
>
> I mentioned in the thread at
> https://groups.google.com/forum/#!topic/leo-editor/r6ktpQNWySk, about
> using the python trace module for debugging python applications, but I no
> longer recommend using it because it is too difficult to filter out noise.
> Since then I've discovered https://github.com/ionelmc/python-hunter and
> it is excellent. You can filter exactly which modules do and don't get
> traced and the colorized output looks nice.
>
> Depending on what pattern of modules you pick to trace you will still get
> a firehose of information. You can either fine-tune your python-hunter
> queries more or just save the trace output to a file which you can search
> through.
>
> ...
>
> Not sure this is really what you are after, but I thought I'd share in
> case in helps.
>

It's not exactly what I'm after, but your description - as well as - the
README of python-hunter makes it clear, that this is an option I'll
investigate further.

Thanks a lot for sharing!

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAAeSrG%2B7i7z8tg_X%3DCZJDRxrZ%3DCF65VvDDMk_QZFgK4q4%2B0VYA%40mail.gmail.com.