4 ms·
You don't need to set all your environment variables in your bashrc, if that's not obvious. They're not global state. You can change them on a per-terminal basi
by traverseda 9y ago
You don't need to set all your environment variables in your bashrc, if that's not obvious. They're not global state. You can change them on a per-terminal basis, and that only effects the environment of that one terminal.
Firefox does some weird stuff with multiprocessing, where if you run the firefox command twice you only get one process. I don't know how that would effect things, but I imagine just setting the env variable and running as a different firefox profile would do it.
There's always firejail/firewarden, if you need a quick and easy sandbox for a program you already have installed, and that will solve that problem, if it is a problem.
- Vinnl 9y agoAdditionally, it's also possible to turn it on using the CLI flag `--headless`, if setting env vars is a concern.
- Vinnl 9y agoOh, and additionally: passing options with a double dash doesn't work on Windows, so use `-headless` to be sure.
- bryanrasmussen 9y agoD'oh of course.