Tim,
You are certainly welcome to put in my patch, though I realize you are otherwise occupied right now with the job search.
Most of the benefit of CVS is lost if just one person uses it. Are you happy with what you have in CVS? How far back does it go? If you are happy with it, we could put it on fractint.org. Or even if you're not happy, I'd like to see what you have.
Once it's on fractint.org (or other accessible place) we could both use it. If you just zip up the files and send it to me I could probably put in on fractint.org.
If only it were that simple. I have one repository for Fractint, but it should be renamed. It is currently named fractint.20.03p01. I have three repositories for Xfractint, all variations on xfractint.20.03p01. Two of them have only two minor fixes. The third also has structural changes where I've put the Unix code in a separate subdirectory and modified the Makefile to work. The repositories should be named Fractint and Xfractint, but knowing how to make tags work would seem to be essential. Would we want to start farther back than 20.03p01? We could start with the version 20.0 source. By the time we got to the current patch we would have a pretty good idea about how to make CVS work for us. Do we want to bring in the structural changes with a patch? Deleting files and recreating them elsewhere creates a very large diff file. Also note that the repository created under Windows causes error messages under Linux. Everything still seems to work, but every operation causes the error message to appear. Jonathan