Is outline "leoPluginRef.leo" inconsistent on GitHub?

32 views
Skip to first unread message

Viktor Ransmayr

unread,
Jan 1, 2017, 12:14:01 PM1/1/17
to leo-editor
Hello Edward,

When I try to open the outline "leo PluginRef.leo" using "File -> Open Leo File -> Open leoPlugins.leo" I get the following feedback:

<Log>

Leo Log Window
Leo 5.4, build 20170101101955, Sun Jan  1 10:19:55 EST 2017
Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0
reading: C:\Users\Viktor\Programs\Leo-20170101\leo\plugins\leoPluginsRef.leo
!!! -> cached read node changed: class Rst_Importer <- !!!
reading: @edit QNCalendarWidget.py
read 163 files in 8.40 seconds
read outline in 8.58 seconds

</Log>

I tried it also using "Plugins -> open-leo-plugins-leo". - Same result ...

Shall I file a bug report?

With kind regards,

VR

PS: This behaviour started at least 2 days ago ...
 

Edward K. Ream

unread,
Jan 1, 2017, 12:51:29 PM1/1/17
to leo-editor
On Sun, Jan 1, 2017 at 12:14 PM, Viktor Ransmayr <viktor....@gmail.com> wrote:
Hello Edward,

When I try to open the outline "leo PluginRef.leo" using "File -> Open Leo File -> Open leoPlugins.leo" I get the following feedback:

 

<Log>

Leo Log Window
Leo 5.4, build 20170101101955, Sun Jan  1 10:19:55 EST 2017
Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0
reading: C:\Users\Viktor\Programs\Leo-20170101\leo\plugins\leoPluginsRef.leo
!!! -> cached read node changed: class Rst_Importer <- !!!
reading: @edit QNCalendarWidget.py

​Does clear-all-caches help?  You could also try the --no-cache option.​
 

​You never need permission to file an official bug report.  That's the new policy ;-)​

​Edward

Viktor Ransmayr

unread,
Jan 1, 2017, 1:11:34 PM1/1/17
to leo-e...@googlegroups.com
Hello Edward,

2017-01-01 18:51 GMT+01:00 Edward K. Ream <edre...@gmail.com>:

On Sun, Jan 1, 2017 at 12:14 PM, Viktor Ransmayr <viktor....@gmail.com> wrote:
Hello Edward,

When I try to open the outline "leo PluginRef.leo" using "File -> Open Leo File -> Open leoPlugins.leo" I get the following feedback: 

<Log>

Leo Log Window
Leo 5.4, build 20170101101955, Sun Jan  1 10:19:55 EST 2017
Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0
reading: C:\Users\Viktor\Programs\Leo-20170101\leo\plugins\leoPluginsRef.leo
!!! -> cached read node changed: class Rst_Importer <- !!!
reading: @edit QNCalendarWidget.py

​Does clear-all-caches help? 

No. - See

<Log-1>


Leo Log Window
Leo 5.4, build 20170101101955, Sun Jan  1 10:19:55 EST 2017
Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0
leoID=VIRA2015 (in C:\Users\Viktor\.leo)
load dir: C:\Users\Viktor\Programs\Leo-20170101\leo\core
global config dir: C:\Users\Viktor\Programs\Leo-20170101\leo\config
home dir: C:\Users\Viktor
reading settings in C:\Users\Viktor\Programs\Leo-20170101\leo\config\leoSettings.leo
reading settings in C:\Users\Viktor\.leo\myLeoSettings.leo
reading settings in C:\Users\Viktor\worklogs\wl2017.leo
reading: C:\Users\Viktor\worklogs\wl2017.leo
read outline in 0.03 seconds

clearing cache at directory...
C:\Users\Viktor\.leo\db\wl2017.leo_259d930e7ec402131cdbfe8d7be4b440
done
reading settings in C:\Users\Viktor\Programs\Leo-20170101\leo\plugins\leoPluginsRef.leo

</Log-1>

and

<Log-2>


Leo Log Window
Leo 5.4, build 20170101101955, Sun Jan  1 10:19:55 EST 2017
Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0
reading: C:\Users\Viktor\Programs\Leo-20170101\leo\plugins\leoPluginsRef.leo
!!! -> cached read node changed: class Rst_Importer <- !!!
reading: @edit QNCalendarWidget.py
read 163 files in 0.33 seconds
read outline in 0.47 seconds

</Log-2>
 
With kind regard,

VR

Viktor Ransmayr

unread,
Jan 1, 2017, 1:31:51 PM1/1/17
to leo-e...@googlegroups.com
Hello Edward,

2017-01-01 18:51 GMT+01:00 Edward K. Ream <edre...@gmail.com>:

On Sun, Jan 1, 2017 at 12:14 PM, Viktor Ransmayr <viktor....@gmail.com> wrote:
Hello Edward,

When I try to open the outline "leo PluginRef.leo" using "File -> Open Leo File -> Open leoPlugins.leo" I get the following feedback: 

<Log>

Leo Log Window
Leo 5.4, build 20170101101955, Sun Jan  1 10:19:55 EST 2017
Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0
reading: C:\Users\Viktor\Programs\Leo-20170101\leo\plugins\leoPluginsRef.leo
!!! -> cached read node changed: class Rst_Importer <- !!!
reading: @edit QNCalendarWidget.py

​Does clear-all-caches help? 

See previouse email.
 
You could also try the --no-cache option.​

Something changed now.

I created a new bat-file which contained this option. - See

<Log-3>


Leo Log Window
Leo 5.4, build 20170101101955, Sun Jan  1 10:19:55 EST 2017
Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0
leoID=VIRA2015 (in C:\Users\Viktor\.leo)
load dir: C:\Users\Viktor\Programs\Leo-20170101\leo\core
global config dir: C:\Users\Viktor\Programs\Leo-20170101\leo\config
home dir: C:\Users\Viktor
reading settings in C:\Users\Viktor\Programs\Leo-20170101\leo\config\leoSettings.leo
reading settings in C:\Users\Viktor\.leo\myLeoSettings.leo
Using default leo file name:
C:\Users\Viktor\.leo\workbook.leo
reading settings in C:\Users\Viktor\Programs\Leo-20170101\leo\doc\CheatSheet.leo

reading settings in C:\Users\Viktor\Programs\Leo-20170101\leo\plugins\leoPluginsRef.leo

</Log-3>

and

<Log-4>


Leo Log Window
Leo 5.4, build 20170101101955, Sun Jan  1 10:19:55 EST 2017
Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0
reading: C:\Users\Viktor\Programs\Leo-20170101\leo\plugins\leoPluginsRef.leo
reading: @file leoPluginNotes.txt
reading: @file attrib_edit.py
...
reading: @file importers/linescanner.py
resurrected node: i.scan_table
in file: @file importers/linescanner.py
resurrected node: i. to be retired
in file: @file importers/linescanner.py
reading: @file importers/markdown.py
...
reading: @file writers/otl.py
read 163 files in 0.97 seconds
read outline in 1.11 seconds

</Log-4>

With kind regards,

VR

Edward K. Ream

unread,
Jan 2, 2017, 6:17:09 AM1/2/17
to leo-editor
On Sun, Jan 1, 2017 at 1:31 PM, Viktor Ransmayr <viktor....@gmail.com> wrote:

​> ​
Something changed now.

​Resurrected nodes should go away if you reload ​the .leo file.

EKR

Viktor Ransmayr

unread,
Jan 2, 2017, 7:19:33 AM1/2/17
to leo-e...@googlegroups.com
Hello Edward,

This is to much magic for me at the moment. - Do you have an explanation about the cause of this issue?

With kind regards,

VR
 

Edward K. Ream

unread,
Jan 2, 2017, 9:13:52 AM1/2/17
to leo-editor
On Mon, Jan 2, 2017 at 7:19 AM, Viktor Ransmayr <viktor....@gmail.com> wrote:

​Resurrected nodes should go away if you reload ​the .leo file.

This is to much magic for me at the moment. - Do you have an explanation about the cause of this issue?

Resurrected nodes arise when .leo files can get out of sync with external files.  When that happens, Leo takes care not to lose data by creating new nodes.  In most cases, you can just ignore the newly created nodes, especially if you are using git.

For more details, you can Google "Leo Resurrected node", but the scenarios involved are complex and the code isn't going to change.

Edward​
 

Viktor Ransmayr

unread,
Jan 6, 2017, 6:19:02 AM1/6/17
to leo-e...@googlegroups.com
Hello Edward,

I found some time now to investigate the behaviour previously reported further:

I updated Leo to the latest ZIP-Archive from GitHub

<Log-1>

C:\Users\Viktor\worklogs>C:\Programs\Python36\python.exe C:\Users\Viktor\Programs\Leo-20170106\launchLeo.py wl2017.leo
leoID=VIRA2017 (in C:\Users\Viktor\.leo)
reading settings in C:\Users\Viktor\Programs\Leo-20170106\leo\config\leoSettings.leo

reading settings in C:\Users\Viktor\.leo\myLeoSettings.leo
reading settings in C:\Users\Viktor\worklogs\wl2017.leo

** isPython3: True
Leo 5.4, build 20170105133315, Thu Jan  5 13:33:15 EST 2017

Not running from a git repo
Python 3.6.0, PyQt version 5.7.1
Windows 10 AMD64 (build 10.0.14393) SP0

</Log-1>

I opened the outline "LeoPluginRef.leo" via Plugin -> open-leo-Plugins-leo

<Log-2>

reading settings in C:\Users\Viktor\Programs\Leo-20170106\leo\plugins\leoPluginsRef.leo
callback *moving* <VNode 19e93f44c88 i. to be retired> 1 <VNode 19e93f44d30 i.scan_table>

resurrected node: i.scan_table
in file: @file importers/linescanner.py
callback *moving* <VNode 19e93f44b70 i.Scanning & scan tables> 0 <VNode 19e93f44c88 i. to be retired>

resurrected node: i. to be retired
in file: @file importers/linescanner.py
wrote recent file: C:\Users\Viktor\.leo\.leoRecentFiles.txt

</Log-2>

I closed the outline "LeoPluginRef.leo". - Note: I did not have to save anything!

Then I re-opend this outline using the same method & received the outline in a modified state.

<Log-3>

reading settings in C:\Users\Viktor\Programs\Leo-20170106\leo\plugins\leoPluginsRef.leo

cached read node changed: class Rst_Importer
PS C:\Users\Viktor\worklogs>

</Log-3>

I closed Leo without making any changes.

In my opinion I should consistently receive every Leo outline in a read-only mode - until - *I* make an explicit change to it.

With kind regards,

VR

Viktor Ransmayr

unread,
Jan 7, 2017, 11:20:10 AM1/7/17
to leo-editor, viktor....@googlemail.com
Hello Edward,

I filed an issue for that topic as well. - See https://github.com/leo-editor/leo-editor/issues/363

With kind regards,

VR

Reply all
Reply to author
Forward
0 new messages