3 ms·
I use firefox, and find this function useful: # Open a new firefox instance, with a temporary profile function firefox_temp() { dir=$(mktemp
by stevekemp 8y ago
I use firefox, and find this function useful:
# Open a new firefox instance, with a temporary profile
function firefox_temp() {
dir=$(mktemp -d)
echo "Profile directory: ${dir}"
firefox --new-instance --profile ${dir}
echo "Cleaning up .."
rm -rf ${dir}
}
I'm not familiar with Chrome, but perhaps there is a similar "profile-directory" argument you can point to a temporary location?
- Ysx 8y agoThat's interesting... does it behave much differently to private windows?
- stevekemp 8y agoIf we assume that the private-mode is "secure", then I suspect there's probably not a huge difference in practice. But this way I'm very certain extensions, history, local-storage, etc, are absolutely not available. (To be honest I tend to use this mostly avoid caching, and other things. Useful when you're testing redirects and new designs.)
- josephorjoe 8y agoYou can use the `--user-data-dir` arg to specify a profile location when opening chrome. So, on a mac, something like: open -Fna /Applications/Google\ Chrome.app \ --args --user-data-dir=/my_temp_profile_dir/my_tmp_profile If you copy an existing profile to `my_tmp_profile` chrome will use that, otherwise it behaves like a new setup.