A couple months ago I wrote an email about architecture, I think that was the subject. Nothing is more fundamental than the way we store the lines in the buffer. 20 years ago I picked a simple design that was fine relative to the computers of the day. Since then it has shown some inadequacies. Thus, for my birthday, I am trying to majorly restructure edbrowse so that lines are link list, not all stored in sequence in an array. No one part of this is hard, but it touches everything and is a lot of work and will be a lot of testing. But even on some medium files it will help performance, and perhaps memory. Example, g/7$/ .m-2 that would take weeks on one of those seq 1000000 files, and no amount of my mass operation fixup would help that one, but with link lists it would fly. Moving text about is just changing some link pointers, you see. And I can get rid of all those specialized mass delete mass join mass read mass substitute routines. So it's a lot of work, and testing, and probably chasing down some seg faults, you know pointers in c and such, and I greatly appreciate your patience when those appear, but will be worth it. Karl Dahlke