Blew out SM 1.1 by editing prefs.js
I screwed up. Now I have to try to restore everything. I had a MozBackup file from July, but it just doesn't restore ! Went to restore, picked the file, but it doesn't show the Next button. Looked at the instructions for MozBackup, but MB doesn't follow what is said. I have to pick 'Default' regardless of the saved file I chose. How do you restore an old file ? How do you get MB to USE that file? DoctorBill ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Blew out SM 1.1 by editing prefs.js
On 8/30/10 4:16 PM, DoctorBill wrote: I screwed up. Now I have to try to restore everything. I had a MozBackup file from July, but it just doesn't restore ! Went to restore, picked the file, but it doesn't show the Next button. Looked at the instructions for MozBackup, but MB doesn't follow what is said. I have to pick 'Default' regardless of the saved file I chose. How do you restore an old file ? How do you get MB to USE that file? DoctorBill DO NOT EDIT prefs.js. The very top of the file says Do not edit this file. Edit user.js. Terminate SeaMonkey and then restart it. The contents of user.js overwrite the corresponding preference variables in prefs.js whenever SeaMonkey starts up. I prefer this method because I can insert comments into user.js to remind me why I have changed a preference. Alternatively, enter about:config in the address area of the browser. The preference variables displayed apply to both the browser and mail-news. -- David E. Ross http://www.rossde.com/. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Blew out SM 1.1 by editing prefs.js
David E. Ross wrote: On 8/30/10 4:16 PM, DoctorBill wrote: I screwed up. Now I have to try to restore everything. I had a MozBackup file from July, but it just doesn't restore ! Went to restore, picked the file, but it doesn't show the Next button. Looked at the instructions for MozBackup, but MB doesn't follow what is said. I have to pick 'Default' regardless of the saved file I chose. How do you restore an old file ? How do you get MB to USE that file? DoctorBill DO NOT EDIT prefs.js. The very top of the file says Do not edit this file. Edit user.js. Terminate SeaMonkey and then restart it. The contents of user.js overwrite the corresponding preference variables in prefs.js whenever SeaMonkey starts up. I prefer this method because I can insert comments into user.js to remind me why I have changed a preference. Alternatively, enter about:config in the address area of the browser. The preference variables displayed apply to both the browser and mail-news. The problem with this is that if you have a user.js file in your profile it will be read when you launch the app and over-ride equivalent prefs in prefs.js. So. You edit/create user.js. You run the app. And over time you use the UI or about:config to change prefs. Let's say those changes get recorded in prefs.js. Great. You close the app. You run the app. The app loads prefs.js THEN loads user.js and over-rides any changes you made using the UI or about:config. -- Ed Mullen http://edmullen.net/ How can you tell when the blue cheese goes bad? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Blew out SM 1.1 by editing prefs.js
On 8/30/10 9:47 PM, Ed Mullen wrote: David E. Ross wrote: On 8/30/10 4:16 PM, DoctorBill wrote: I screwed up. Now I have to try to restore everything. I had a MozBackup file from July, but it just doesn't restore ! Went to restore, picked the file, but it doesn't show the Next button. Looked at the instructions for MozBackup, but MB doesn't follow what is said. I have to pick 'Default' regardless of the saved file I chose. How do you restore an old file ? How do you get MB to USE that file? DoctorBill DO NOT EDIT prefs.js. The very top of the file says Do not edit this file. Edit user.js. Terminate SeaMonkey and then restart it. The contents of user.js overwrite the corresponding preference variables in prefs.js whenever SeaMonkey starts up. I prefer this method because I can insert comments into user.js to remind me why I have changed a preference. Alternatively, enter about:config in the address area of the browser. The preference variables displayed apply to both the browser and mail-news. The problem with this is that if you have a user.js file in your profile it will be read when you launch the app and over-ride equivalent prefs in prefs.js. So. You edit/create user.js. You run the app. And over time you use the UI or about:config to change prefs. Let's say those changes get recorded in prefs.js. Great. You close the app. You run the app. The app loads prefs.js THEN loads user.js and over-rides any changes you made using the UI or about:config. That is why I use the about:config capability only to test changes to preference variables. When I finally decide on a change, I then always make the change in user.js. HOWEVER, I never use about:config or user.js if I can get the change I want through the Preference UI. Long, long ago -- before Netscape, even before the general public began to use the Internet -- I learned as a software test engineer always to use a user interface to change software settings whenever such an interface existed. That is because a single change might actually involve more than one flag or variable, and a change might require some obscure internal housekeeping that is automatically handled by the user interface. -- David E. Ross http://www.rossde.com/. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
