Browsers requests default browser setting on every launch about browsers HOT 6 CLOSED

I see there's a rules section in the config.json file but it's not clear to me what that does or how I'd use it: does that functionality replace Finicky in my scenario? Could I build regex patterns that automatically direct certain URLs to certain browsers here? If so, I could probably streamline my setup and also work around this issue at the same time.

from browsers.

I will eventually plan to add a GUI for settings, but yep you found the settings file can do some things already.
There is some documentation at #34

I didn't pick regex for the syntax, but kind of glob-like patterns. I would be interested to get some feedback if that covers the need for you or not.

The easiest way to find the profile id is from the cache file. Or if you re-order the browser, then the id is also visible in the config file.

from browsers.

I'll look into that! I could share a [sanitized] version of my finicky.js if you think that would help you as a more experienced reader say if the rules functionality replicates what I'm doing.

In the meantime, is there a way to block Browsers from continuing to prompt to be set as default? That also handles the issue perfectly.

from browsers.

OK, I took some time today and converted all my regular expression browser rules to your glob format. It worked great for my basic use cases, which is just intercepting a bunch of root and sub-domains and directing them to my "work" browser config. I could see situations where the regular expressions would be more powerful if you wanted more fine-grained control over these patterns (e.g. "open this Google doc in Chrome and this one in Safari") but those are probably edge cases.

A quick proper doc for this would be super helpful, even though it's just JSON and pretty clear from your PR. That PR comment is about 90% of the way to being product-ready doc IMO, though it has a few minor errors that stop it from being used directly (missing commas, comments disallowed, some more examples)

As a result I've changed my default browser to Browsers and pulled Finicky out of the mix entirely. I still think better control over the default browser prompt would be worth adding to Browsers but it is no longer a specific problem I have.

Now, we just need to figure out how to get the menu to exit more easily when it loses focus and this is a perfect solution!

from browsers.

Hmm. I definitely didn't intend it to request to be default browser on every launch. Thanks for reporting it.

from browsers.

Should be fixed in 0.4.1

from browsers.