View Single Post
Old 10-28-2019, 01:28 PM   #92
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@MGlitch: What's your usual workflow?

macOS has *always* quarantined downloaded binaries (well, at least since the GateKeeper days).

The usual least-annoying way to deal with it on unsigned binaries was not to double-click 'em, as that was hitting a GateKeeper wall even before Catalina, but to right-click > Open them, which lead to a different GateKeeper popup, one with an actually clickable "Open" button.

(c.f., this recap in the OCP thread, which also still includes older thumbnails for the Open with > Terminal approach for a .sh).

I can't check myself, as I haven't updated to Catalina (because ADE).
But it's my understanding that this should still work without having to mess with the System Prefs.

Granted, here, this is easier with a .script than a .sh (see the relevant issue).

Last edited by NiLuJe; 10-28-2019 at 01:32 PM.
NiLuJe is offline   Reply With Quote