And that just extensions. Same goes for many aspects of Firefox configuration, language, about:config, etc. Would it not be better to have several Firefox profiles, one for each task? If you ask me, it would.
One problem though – even if you find the hidden Firefox profile manager, Firefox will not let you launch multiple instances of it without a bit of coercion. Previously, I resorted to all kinds of commandline trickery to manage my profiles until I found a script somewhere on the web (I've been unable to find it again. If you know it, please post a comment – I'd like to give proper attribution) that helped me set up copies of Firefox.app for each profile, but it had its limits. It did not work for Firefox.app itself, only for its named copies. It also renamed the Firefox binary, causing trouble for other scripts. So I've rewritten it in Python, improving a few key things:
- It modifies
Info.plistto use a launching script instead of renaming
- It sets the normal Firefox.app to use the profile named “default”.
Instructions for use
- Download Herd Fire.
- Copy your Firefox.app to create a named copy (I'm using the name “example” here):
- Run Herd Fire ( run it from the folder its located in, or stick it in a folder on your path):
- Launch your new Firefox copy.
- If there is not a Firefox profile with the extra name you gave your
Firefox.app copy (in this case “example”), the profile manager will appear.
In that case, use it to create a new profile with the correct name.
- Firefox-example.app will now always start with the “example” profile
activated. Firefox auto updater might break this. In that case, all
you need to do is to run
The code is in a GitHub repository, so please don't hesitate to fork, file bugs, etc.