OMG. It is dead easy to *visually* remove gnx's from thin external files! Leo can put all gnx's in a single (long) leo-editor line, just like a vim line. The only difference between this scheme and various put- gnx's-in-table schemes that I've considered over the years is that the "table" contains no newlines :-)
This is simply fantastic: - Only a single line ever creates gnx-related diffs due to inserted, deleted, moved nodes. - Most of the visual clutter will disappear from other editors: the gnx's disappear because they are off the screen to the right. Leo could even pad the gnx's with 80 blanks ;-) A few minor details: - We can *not* just have order of the gnx's in the leo-editor line correspond to the order of the nodes in the file--it would make it too dangerous to move nodes in another editor. Thus, we need the previous base-62 (52 letters and 10 digits) index scheme to associate lines with nodes. To reduce diffs we want to keep these base-62 indices unchanged. The easy way to do this is never to delete gnx's from leo-editor lines, but simply to add gnx's to the end ;-) Alternatively, once a gnx goes unused, we could replace it by a placeholder, say a period, but that would be a premature optimization now. This is a big day for Leo. This Aha, combined with simplified sentinels, should make many people less hostile to Leo sentinels. In the new scheme, Leo sentinels will look like emacs outline notation, except for the base-62 indices which will only add a few (typically 2 to 4) "strange" characters per sentinel. 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.
