Leo 4.7.1 will indeed be needed to fix a bug that can (will) cause
data loss in the conversion of @file nodes to the new (thin-like)
sentinels.

The following bug-tracker discusses various versions of this bug:
https://bugs.launchpad.net/leo-editor/+bug/395432 @file nodes destroy
data

Stephen P. Schaefer reported the problem a few hours ago, but did not
reopen the bug.  I am going to keep the bug closed, because it appears
to have been fixed.

Here is the checkin log:

QQQ
A bug fix that will require Leo 4.7.1: much better conversion of file-
like sentinels to thin-like sentinels:

1. cacher.readFile now returns the contents of the file.
2. at.read calls the new at.isFileLike(s) to determine whether the
file has file-like sentinels.
3. when isFileLike is True, at.read disables caching, says that the
file will be converted, and sets the root dirty.

The effect of all these changes is that it will be impossible for a
naive user to save a .leo file without converting @file nodes.

A sophisticated user might cause problems by using the write-outline-
only command, but that's not the issue here.
QQQ

Stephen, you can install this fix simply by getting leoAtFile.py and
leoCacher.py from the trunk.  I would like to hear your comments on
this fix before releasing Leo 4.7.1.

I expect to release Leo 4.7.1 in a day or two.  In the meantime,
please hold commits to the trunk.  Thanks.

My apologies for these problems.  As I write this, I think the safe
thing to do will be to withdraw Leo 4.7 final.

Edward

P.S.  The short description of this bug is this:  Leo 4.7 must,
without fail, write all @file nodes the first time Leo 4.7 writes
any .leo file.  The reason is that Leo 4.7 never writes tnodeLists to
the .leo file, and without those lists Leo can't read external files
with old (file-like) sentinels.

EKR

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.

Reply via email to