On Wednesday 05 March 2008 03:14 pm, you wrote: > On Wednesday 05 March 2008 12:03 pm, Bert Wesarg wrote: > > A next point I don't understand is, is it right, that the folding > > engine should also handle partial intersected folding regions? > > > > - > > | > > |- > > || > > L| > > | > > L
Oh, now I see, this is (I think) what might be called an improperly nested set of folds. I'm not sure how that would come about in real life--do you see the possibility of this occurring? (In a "normal" text document, I would be trying to avoid this situation, and can't recall ever having had to consciously work to avoid it. Can it occur in code?) Old stuff that might be relevant (or not): > I'll have to think about that some more, unless my previous discussion > answered the question. I mean, in general, folding regions can overlap, and > nedit should handle such overlapping folding regions, but, trying to think of > the right words, I expect that overlap is sort of "normalized" or "proper", > sort of like, iirc, HTML markup can be "proper" (not the word I'm seaching > for, maybe I mean "properly nested"). > > Trying other words, I expect all lower level folds in the hierarchy would end > at (and not extend beyond) the end of the highest level fold in the > hierarchy. > > If that is your question, I guess the next logical question is, would it be an > advantage to be able to handle such improperly nested folds, and, off the top > of my head, I'd say no. I can think about it some more. regards, Randy Kramer -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
