Bug #760248 by pbw is relevant to my new indenting code:
A line that begins with an improperly indented </xsl:text> outside a
comment or CDATA section will mess up subsequent indenting.
I fixed this in my working copy, but I have made a bunch of other
changes (new table of tags) and reworked the indenting code for
efficiency without changing it's function (except by fixing this bug).
Why efficiency in indenting? xsl-invasive-indent used to get unusably
slow on one-line xml files over 500K. That's fixed now too. I use
xsl-invasive-indent several times a day most days, but I doubt anyone
will even know it exists if they don't read this post. How should I
advertise it (or any other function of xslide for that matter)? Is
there any kind of xslide manual? Where will users look first for this
sort of information?
I want to make a branch for the changes I have made since my last
check-in so that I have a backup of them before checking out a working
copy to fix this bug. I have added a file (for auto-completion
functions) and will probably first add it to the branch. Will CVS work
properly when I want to merge this new file into the trunk?
Maybe I'll post my backup as a patch (as I used to do) and fix this
problem, then worry about CVS afterward. Ugly, but effective.
|
