I would just correct the table - option 3 isn't for a remote file. It's for local file which has been downloaded by a browser and hasn't been edited yet. And I think this is related to security - I believe Apple fears that users could associate files with some interpreter and then just by double-clicking the downloaded file it would get executed.

There's also:
Option 4 - file dragged to Geany launcher icon - if not running, geany is launched and callback is called
Option 5 - file dragged to Geany window - the callback is called

The problem with Geany is that it isn't a native macOS application. Instead of launching the binary directly, macOS launches a shell script which sets various environment variables and then launches the Geany process with normal shell exec command. On the other hand when you double-click an application bundle of a native macOS application, it won't create a new process if some instance is already running (no socket like Geany uses is needed) so native applications don't have this problem.

Your last paragraph pretty much summarises what I think is the situation Geany is facing and I don't see a solution.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.