Itr's a only little more subtle: the first time a vnode of a
particular gnx is encountered, it gets put out in its entirety, just
as before - <vh></vh> and child vnodes. On subsequent occasions
(which happen because of clones) I put out
"<v t="%s" %s></v>" % (gnx,attrs)
which preserves open/close status and whatever other attributes the
vnode has -- but this does not put out the <vh></vh> or child vnodes,
because the current design of leo (at least since "graph"
implementation) reaches those attributes through a common tnode and
they are thus necessarily identical.
- Stephen
On Oct 18, 6:53 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 17, 2008 at 8:33 PM, thyrsus <[EMAIL PROTECTED]> wrote:
> > Please take a look at the changes I made to leoFileCommands.py in
> > thyrsus1.
>
> Will do.
>
> > Amazingly, the SAX
> > parser required *NO* changes to read the suppressed redundancy file.
>
> Yeah, sax was probably a "lucky" choice for this because it only knows
> about nodes, not overall tree structure ElementTree might have had
> problems.
>
> > All unit tests pass. The suppression makes a huge difference for my
> > most important file:
>
> > bash-3.2$ wc ISconf.leo ISconf-after.leo
> > 250024 466784 10037715 ISconf.leo
> > 24207 64076 929273 ISconf-after.leo
>
> Could you say more about what suppression? Unless I am mistaken, only
> one copy of each tnode (<t> element) ever gets written. So your code
> is writing a vnode (<v> element) only if it hasn't already been
> written?
>
> 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
-~----------~----~----~----~------~----~------~--~---
