Forum: Weblog comments

Well, this is cool. The last time I tried a SeaMonkey 2 CVS build, it had two of the big problems that I have with Firefox: crashing every few minutes and no search in the location bar. As appealing as the ability to use Firefox extensions in SeaMonkey (or at least, alter them to work in SeaMonkey pretty easily) is, XPFE is rock solid.

I probably should try to download and compile off the trunk again. I currently have the source for 1.1.7, which won't compile. Maybe I'll have better luck for the trunk (after all, my .mozconfig file was written for 2 and I tried to adapt it for 1.1.7; maybe that just didn't work).

The last time I tried SeaMonkey 2, settings were saved to ~/.mozilla.org/seamonkey. That's good, as it can coexist with the Mozilla Suite/SeaMonkey, but I think it would be better to just put it into ~/.mozilla/seamonkey similar to how Firefox does, or simply ~/.seamonkey. Then, when the final is released, you can store the new or migrated profiles in seamonkey2.

Since I brought up CVS, I seem to recall that the project is intending to move to Mercurial. How's that going?

Keith:
The change to using ~/.mozilla/seamonkey has been done a while ago, so the build you tried must really have been some time in the past

The change to Mercurial will only happen after SeaMonkey 2, as it's a Gecko 2 thing, and SeaMonkey 2 is based on Gecko 1.9 (same as Firefox 3).

Yeah, I guess it was a while back. It doesn't seem that long ago, but time does fly. It was just around the time that you guys set it to build with the Firefox toolkit by default.