61–70 of 75 posts
I would suggest another command. Instead of "XXX:extract" I use my little shell script, which runs correct unarchiver basing on the file name (or series of unarchivers for common cases like .tar.gz). So you don't have to memorise every command out there. Another useful functionality is to create a separate directory, if archive contains multiple "root" files, so the current directory won't be polluted by the bad arch…
I would advise finding another name for the tool. 'mac' is an obvious trademark infringement and it's only a matter of time before Apple lawyers come knocking on your door. Honestly I find it uncool to piggyback on someone else's brand in this way. The protagonists are different but it's the same fundamental issue as the "Ubuntu vs OVH" and "Let's Encrypt vs Comodo" stories we've seen recently.
There is other non-Apple software that has been happily using "mac" in its name for a long time, no? Everybody knows MacPorts, and there's Mactracker and MacCleanse on the App Store itself, and the infamous Mackeeper (which may very well be malware; Apple should go after them first) and companies: MacPhun and MacPaw. But I guess people may confuse "Mac CLI" as being an official part of macOS.
What's so wrong with the regular command line commands for most of this?
Well, would you rather remember: `sudo shutdown -r now` or `mac shutdown`? Would you rather remember: `pmset sleepnow` or `mac restart`?
Earlier quoted context omitted.
Well, would you rather remember: `sudo shutdown -r now` or `mac shutdown`? Would you rather remember: `pmset sleepnow` or `mac restart`?
Is there complementary `linux shutdown` and `freebsd shutdown` and `solaris shutdown`? If no, then this utility only increases cognitive load.
how in the world does it 'increase cognitive load'? Seems like its just your opinion. I know how to shut down a generic linux box. But mac shutdoown or mac reboot is still easier to type and remember.
How about 'climate'?
What's so wrong with the regular command line commands for most of this?
alias eject="hdiutil info | gawk '/^\/dev\/disk([0-9]*)\>/ { system(\"hdiutil detach \" \$1) }'"
HomeBrew screws with your systems file permissions and installs directly into the standard system directories.
MacPorts (https://www.macports.org/) is at least a good, and it installs into the /opt tree, staying out of the way of anything Apple or Darwin wants to do when updating or patching your system.
Don't like MacPorts? There's always Fink (http://www.finkproject.org/), which installs into /sw and looks like Debian (i.e. apt-get).
HomeBrew seems like the worst of the three. :-(