finicky

finicky copied to clipboard

Thanks for the quick update to 3.3.1! amazing stuff! now with that working, i'm trying to differentiate "opener" and i'm not getting any good info on it. even a simple open "https://bbc.co.uk" command logs this:

2021-02-01 21:21:06 - Opening https://bbc.co.uk from N/A
	bundleId: N/A
	path: N/A

i've tried several different cli commands, all of them show N/A for everything. would be nice to get the full command (including arguments) of the "opener"

Hm maybe I could take a second look at the command line invocation use case

On Mon, Feb 1, 2021, 21:26 strannik19 [email protected] wrote:

Thanks for the quick update to 3.3.1! amazing stuff! now with that working, i'm trying to differentiate "opener" and i'm not getting any good info on it. even a simple open "https://bbc.co.uk" command logs this:

2021-02-01 21:21:06 - Opening https://bbc.co.uk from N/A bundleId: N/A path: N/A

i've tried several different cli commands, all of them show N/A for everything. would be nice to get the full command (including arguments) of the "opener"

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/johnste/finicky/issues/168, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGYKI2MGGU76AVOG7IPYKDS44E7JANCNFSM4W5NJKXQ .

I commented a good bit in #272 before realizing it was a dupe of this issue. The issue is that the subprocess is what is opening the url, not iTerm/terminal. As I mentioned in that other issue, you'd probably need to use additional process details and process hierarchy to figure out if it came from the terminal.

FWIW, I've added this, because if I can't actually tell what the hell is opening a url, I'll be picking what's opening it :)

    {
      match: ({ opener }) => !opener.path && !opener.name && !opener.bundleId,
      browser: "Browserosaurus"
    },