FinderPath.
It makes Finder's title clickable to be able to copy or change the current path, just like Windows' explorer.exe.
Hard to discover tips and apps for macOS
111–120 of 232 posts
Re: Hard to discover tips and apps for macOS
#112I recommend macports package management system, similar in function to BSD ports collection. Superior to Homebrew, the johnny-come-lately PMS with all the penguinista-style hype that seems to lean towards binary installs, unlike roll your own from all source in macports. Homebrew also does not honor the default privileges of /usr/local, which is an annoying security flaw.
Agreed 100%. No idea why homebrew is so dominant while doing the wrong thing by default. Binaries are nice but not worth the trouble Homebrew gives compared to sane, rational MacPorts.
Re: Hard to discover tips and apps for macOS
#113I’ve been searching for a long time a tool that would resize all the windows open on a given space to fill up the entire screen.
I open lots of things when working and that would be more useful than doing the exposé and switching back and forth do declutter.
It seems to me that this feature is available on Windows and has been for a long time.
I tried almost everything that I could google and I even bought apps that I don’t use anymore because I though that the level of customization would enable it.
Is there someone that knows a tool or a trick to allow that ?
Re: Hard to discover tips and apps for macOS
#114What I miss the most is a workable "focus follows mouse" solution.
Circa Snow Leopard, I used "mondomouse" but that is abandonware and does not work.
I tried to use "dwellclick" but it's not a good solution.
I think there are now some new accessibility settings that actual enable a proper focus follows mouse in Mojave and later, but I don't have anything later than El Cap installed and am unable to test that ...
Re: Hard to discover tips and apps for macOS
#115I’ve been searching for a long time a tool that would resize all the windows open on a given space to fill up the entire screen. I open lots of things when working and that would be more useful than doing the exposé and switching back and forth do declutter. It seems to me that this feature is available on Windows and has been for a long time. I tried almost everything that I could google and I even bought apps that…
BetterTouchTool?
Re: Hard to discover tips and apps for macOS
#116> cmd+shift+4 pops up a crosshair to take a screenshot of a region. If you hit space at after invoking the crosshairs then you can take full window screenshots. This mode is nice for marketing material as it also captures the drop shadow and rounded corners rendered properly as a transparent png.
Came here to share the cmd+shift+4 space trick and learned 3 new tricks instead! I love this community.
Re: Hard to discover tips and apps for macOS
#117Re: Hard to discover tips and apps for macOS
#118Earlier quoted context omitted.
A free alternative to BTT trackpad gestures is jitouch2 ( https://www.jitouch.com ). It's not as versatile and no longer maintained, but works well for most use cases even in the latest version of MacOS.
I just don't get why custom gesture mapping isn't implemented in macOS itself.
"custom" violates Apple's UX philosophy.
Re: Hard to discover tips and apps for macOS
#119Earlier quoted context omitted.
IMO, applications that don't prompt for confirmation on potentially destructive Quit are broken. By this definition, all Mac Web browsers are broken, but you can fix the accidental Command-Q problem on an app-by-app basis by remapping Quit to something harder to accidentally type like Command-Shift-Q using the Keyboard pane in System Preferences. Personally, for applications like my primary browser where intentionall…
> By this definition, all Mac Web browsers are broken Chrome has a “Confirm before Quitting” toggle-option hiding in its File menu, right above Quit. Kind of wish Safari had the same.
Chrome also asks for confirmatiom before destructively closing any tab, even if you don't quit.
Re: Hard to discover tips and apps for macOS
#120Does anyone have a tip to keep macOS from phoning home when you run unsigned binaries? I almost locked up my entire computer this week, presumably because of this... here's the story for that: I had setup unbound listening on 127.0.0.1:53 as the only DNS resolver for all network interfaces, so that I hijack several responses that I might want to (e.g. adnet sinkholes) and forward the rest to Google/Cloudflare over TL…
First: binaries that ship with the system are not included in this because they're platform binaries. Tools like ps or grep won't be included. Second: once the binary has been checked for malware it won't be checked again. Third: if the connection fails immediately the malware check is skipped immediately. So if you are offline or otherwise force the relevant server DNS names to be rejected immediately it shouldn't w…
I was partly aware of many of these, and like I said I'm not 100% sure if this really is the culprit. Your comment is a solid reference on this topic though (better than most of what's on SO), but here's a few comments regarding my specific incident...
On your first point: Was aware of this, and this is the part that is most puzzling about the whole incident to me. I just checked my $PATH and I am indeed running the system binaries, so not sure how to explain this one.
On your second point: Was aware of this too, but I assume a lot of the slowness comes from JITted programs, for which there will be phoning-home for any new executable memory page (AFAIK), and the policy decision caching semantics for things that are not on disk are not as clear to me.
On your third point: While this is true for the connection that gets established to Apple's servers, I think this might have had to do with DNS being UDP based by default (AFAIK), so there is no explicit refusal, and it hangs on a timeout because of that, even though DNS can be done over TCP as well. Haven't investigated this though, just a hunch...
On your fourth and fifth points: I don't use XCode, but my terminal (Kitty) was already on the Developer Tool list when this happened, which makes the situation with ps and grep even more mysterious to me...