The read/write follies continue. I had forgotten essentially everything about @noref, but it appears that the read/write logic for @noref files uses tnodeLists. This makes @noref approximately as dangerous as @file. I would like to kill tnodeLists completely, except for the read code needed to convert old @file nodes with file-like sentinels. That is, I want Leo *never* to write tnodeLists when writing .leo files.
I'm not sure that Leo can read and write @noref files using thin-like sentinels. Preliminary experiments are not encouraging. So unless I hear compelling reasons to keep @noref, I would like to kill it completely. Anyone use @noref? Any other thoughts or objections? Edward -- 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.
