theamk
a day ago
that really does not seem to be something that tools care about. There is already $BROWSER env var, and all tools should support this - and then user can point it to whatever logic they want.
This will give much more control to the user compared to fixed "profile" setting - the script can check working directory, or URL, or calling process, or anything else you can think about!
kevinburke
a day ago
If I'm reading this right that only lets you set the application name, not a specific profile inside the browser.
theamk
20 hours ago
you set BROWSER to your local script, like /home/kevinburke/bin/my-browser
And that file is a shell (or python) script that runs whatever you need - for example that "open" command with profile argument. Or for a more complex setup, it can check the URL and use different profile depending on URL.