![]() ![]() ![]() Tealdeer (because both install `tldr` binaries) Simplified and community-driven man pages Run info on tldr, and you can see all the dependency management, the source code, and even public analytics: $ brew info tldr Another thing I appreciate about Homebrew is that you can appreciate this feature without understanding exactly what it means.īut if you're into it, it can be fun to look at the complexity. That saves a lot of time and CPU fan noise. Homebrew, thankfully, prebuilds the binaries, so you don't have to build from source code on your local machine. Now you can install it: $ brew install tldrĪlready downloaded: /Users/mbbroberg/Library/Caches/Homebrew/downloads/901bc14594a9283e9ab20aec942dc5a9a2befb7e96e1b0fcccb4e3257918813c-tldr-1.3.0_2. Success! The checkmark lets you know it is available. You can confirm it's available by running search again: $ brew search tldr tldr for examples of how to use a command-line utilityĪs an example, take a look at tldr pages, a user-friendly alternative to scrolling through an application's man pages.hub for a better Git experience for GitHub users.pandoc for scriptable document conversions (I often switch from. ![]() pyenv, rbenv, and nodenv to manage Python, Ruby, and Node.js versions (respectively).With that in mind, here are some of my favorites if you're looking for inspiration: Word of mouth is another great method to find utilitites. They are also available through the Homebrew API and listed on the website. Formulae are codified and centralized into the core repositories that are split by operating system (Mac in Homebrew Core and Linux in Linux Core). So it's best to have an idea of what you want before searching that huge list. There are over 5,000 formulae, which is an incredible amount of software. You can see all the "formulae" that are available from Homebrew using the search command, and I use the wc command shows how many formulae there are: # -l counts the number of lines Installation happens with the brew command, which gives us access to thousands of command-line utilities, but not more complex applications.įor us nerds, the utilities that fit into "the stuff you need" category include the handy tree command that shows directory structures and pyenv, which I use to manage multiple versions of Python. Homebrew boasts that it "installs the stuff you need that Apple (or your Linux system) didn't" install by default. $ bash homebrew_installer.sh Manage your command-line utilities with brew $ more homebrew_installer.sh # review the script until you feel comfortable If you prefer to be more cautious, you can curl the file, then run it manually after reviewing it: $ curl -fsSL -output homebrew_installer.sh This command executes the installer script provided by the Homebrew team. If you're on a Mac and don't already have Homebrew, you can install it with: $ /bin/bash -c "$(curl -fsSL )" It provides an incredibly smooth and straightforward experience for anyone familiar with the command line, and it's a good way to learn the command line if you're new to it. Homebrew fills the void as the de facto package manager for macOS (and as another option for Linux). There is no default package manager for Mac users, while Linux users have many options-from the familiar yum and apt to the modern choice of Flatpak. One place where the Mac operating system, macOS, has always been behind Linux is in package management. Instead of pointing and clicking to manually manage my applications and utilities, I prefer to use package management software to install, update, and remove unneeded software. In my quest to "automate all the things," I have been on a journey to manage my Mac laptop as the code it inherently is. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |