1

system "go", "build", *std_go_args(output: bin/"hugo", ldflags:, tags:)

The reason we need to patch this file is because it prevents the error:

command not found: /opt/homebrew/Cellar/hugo@0.145.0/0.145.0/bin/hugo

It’s a mismatch between the path Homebrew expects (bin/hugo) vs the path that is created when using brew extract on Hugo (bin/hugo@0.145.0).

Install the older version

Now that Hugo is extracted and patched, we can install with brew install hugo@0.145.0:

$ brew install hugo@0.145.0

✔︎ JSON API cask.jws.json
✔︎ JSON API formula.jws.json
==> Fetching downloads for: hugo@0.145.0
✔︎ Formula hugo@0.145.0 (0.145.0)
==> Installing hugo@0.145.0 from nelson/local
==> go build -o=/opt/homebrew/Cellar/hugo@0.145.0/0.145.0/bin/hugo -tags=extended withdeploy -ldflags=-s -w -X github.com/gohugoio/hugo/common/hugo.commitHash=nelson -X github.com/gohugoio/hugo/common/
==> /opt/homebrew/Cellar/hugo@0.145.0/0.145.0/bin/hugo gen man --dir /opt/homebrew/Cellar/hugo@0.145.0/0.145.0/share/man/man1
Warning: These files were overwritten during the `brew link` step:
/opt/homebrew/etc/bash_completion.d/hugo
.
.
.
/opt/homebrew/share/zsh/site-functions/_hugo

They have been backed up to: /Users/nelson/Library/Caches/Homebrew/Backup
==> Summary
🍺  /opt/homebrew/Cellar/hugo@0.145.0/0.145.0: 53 files, 73MB, built in 8 seconds
==> Running `brew cleanup hugo@0.145.0`...
Disable this behaviour by setting `HOMEBREW_NO_INSTALL_CLEANUP=1`.
Hide these hints with `HOMEBREW_NO_ENV_HINTS=1` (see `man brew`).
==> Caveats
zsh completions have been installed to:
  /opt/homebrew/share/zsh/site-functions

Hugo v0.145.0 is now installed. There’s a warning with long output in the previous example due to the normal Hugo package being already installed but that is expected. Homebrew is now pointing the hugo binary to v0.145.0 instead of the latest version (v0.160.1 at the time of writing). We can verify with hugo version:

$ hugo version

hugo v0.145.0+extended+withdeploy darwin/arm64 BuildDate=2025-02-26T15:41:25Z VendorInfo=brew

We can also see that Hugo v0.145.0 is installed along with the latest version with brew list | grep hugo:

$ brew list | grep hugo

hugo
hugo@0.145.0

Switching Between Versions with brew link

Currently the hugo command is pointing to v0.145.0. To have it point back to the regular version, run brew unlink hugo && brew link --overwrite hugo:

$ brew unlink hugo && brew link --overwrite hugo

Unlinking /opt/homebrew/Cellar/hugo/0.160.1... 2 symlinks removed.
Linking /opt/homebrew/Cellar/hugo/0.160.1... 49 symlinks created.

And if we want hugo to point back to the old version, run brew unlink hugo@0.145.0 && brew link --overwrite hugo@0.145.0

$ brew unlink hugo@0.145.0 && brew link --overwrite hugo@0.145.0

Unlinking /opt/homebrew/Cellar/hugo@0.145.0/0.145.0... 1 symlinks removed.
Linking /opt/homebrew/Cellar/hugo@0.145.0/0.145.0... 48 symlinks created.

At first I expected brew link --overwrite hugo to work right off the bat, but running both brew unlink and brew link --overwrite is necessary to switch between versions properly. This is because homebrew tracks linked formulas and actual symlinks on disk separately. To help Homebrew track things properly we need to run both brew unlink to clean the records, then brew link --overwrite to write the new symlinks.

There’s no need to use brew pin to prevent the older version of Hugo from updating. Since this is a local copy, there is no remote repository that would be updated that would in turn update our local version. You can even try running brew update to see the warning message:

$ brew update

==> Updating Homebrew...
Warning: No remote 'origin' in /opt/homebrew/Library/Taps/nelson/homebrew-local, skipping update!
Already up-to-date.

Removing the Older Version

If you no longer need Hugo v0.145.0 you can run brew uninstall hugo@0.145.0:

$ brew uninstall hugo@0.145.0

Uninstalling /opt/homebrew/Cellar/hugo@0.145.0/0.145.0... (53 files, 73MB)

If you don’t have any other packages you extracted with brew extract, you can also remove your local tap with brew untap $USER/local

$ brew untap $USER/local

Untapping nelson/local...
Untapped 1 formula (34 files, 36.7KB).

Finally, if you don’t plan on using brew extract again in the future, you can remove the local clone of homebrew-core with brew untap homebrew/core. This will clean up the 1.3GB of files that was downloaded:

$ brew untap homebrew/core

Untapping homebrew/core...
Untapped 5 commands and 8313 formulae (8,975 files, 1.3GB).

Then re-link hugo to the latest version with brew unlink hugo && brew link hugo:

$ brew unlink hugo && brew link hugo

Unlinking /opt/homebrew/Cellar/hugo/0.160.1... 2 symlinks removed.
Linking /opt/homebrew/Cellar/hugo/0.160.1... 49 symlinks created.

References

• https://docs.brew.sh/Manpage
• https://github.com/orgs/Homebrew/discussions/2941
• https://emmer.dev/blog/installing-old-homebrew-formula-versions/

https://nelson.cloud/quick-tip-mute-the-terminal-login-message-with-a-.hushlogin-file/?ref=rss Sun, 28 Sep 2025 00:00:00 +0000 https://nelson.cloud/quick-tip-mute-the-terminal-login-message-with-a-.hushlogin-file/?ref=rss Create a .hushlogin file in your home directory to silence login messages.Today I learned that you can create an empty .hushlogin file in your home directory on macOS and Linux to hide the login message you get when starting up a new terminal window or tab.

I tried this on macOS but it should work on Linux too.

For example, when I start up a new terminal window/tab I see the following message:

After I create the .hushlogin file in my home directory, the login message goes away. First I created the file:

touch ~/.hushlogin

Then I opened a new terminal window to verify that the message no longer shows up:

References

• https://stackoverflow.com/questions/15769615/remove-last-login-message-for-new-tabs-in-terminal
• https://www.cyberciti.biz/howto/turn-off-the-login-banner-in-linux-unix-with-hushlogin-file/

]]>

https://nelson.cloud/remove-shadows-from-screenshots-in-macos/?ref=rss Sat, 05 Oct 2024 00:00:00 +0000 https://nelson.cloud/remove-shadows-from-screenshots-in-macos/?ref=rss Run this command to remove shadows from your screenshots in macOS: <code>defaults write com.apple.screencapture &quot;disable-shadow&quot; -bool &quot;true&quot;</code>On macOS, screenshots of windows have an added drop shadow by default for whatever reason. Here’s how to remove it:

To remove shadows from screenshots copy and paste this into the command line:

1	defaults write com.apple.screencapture "disable-shadow" -bool "true"

To reset this setting and have shadows in your screenshots again run this:

1	defaults delete com.apple.screencapture "disable-shadow"

Alternatively, you can press command + shift + 4 and then press space. Then hold option before you click on a window to take a screenshot. This removes the drop shadow.

References

• https://www.reddit.com/r/MacOS/comments/q7h3xl/any_way_to_take_a_screenshot_on_mac_without_the/
• https://www.idownloadblog.com/2014/08/03/how-to-remove-the-shadow-window-screenshots-on-mac-os-x/

There were several other sites covering this but they didn’t get right to the point and/or they were ad-ridden, so I decided to write a straightforward post about this.

]]> https://nelson.cloud/find-unnecessary-homebrew-packages-with-brew-leaves/?ref=rss Mon, 22 Jan 2024 00:00:00 +0000 https://nelson.cloud/find-unnecessary-homebrew-packages-with-brew-leaves/?ref=rss Use the &lsquo;brew leaves&rsquo; command to find potentially unnecessary Homebrew packages. Homebrew has a “brew leaves” command that shows all installed packages that are not depended on by other packages. That means that they can be uninstalled without causing issues to other installed Homebrew packages. It’s good to regularly run this command to keep Homebrew from getting too bloated.

Here’s what my brew leaves output looks like at the time of this writing:

$ brew leaves

automake
bat
black
coreutils
ffmpeg
go
htop
hugo
jq
libksba
libpq
libtool
libyaml
node
openssl@1.1
pkg-config
postgresql@14
python-typing-extensions
tldr
tree
yt-dlp
zlib

In my case, I know I don’t need the libpq package anymore. So I can remove this package and then run brew leaves again to confirm it’s gone.

$ brew remove libpq

Uninstalling /opt/homebrew/Cellar/libpq/16.1_1... (2,380 files, 29.9MB)

$ brew leaves

automake
bat
black
coreutils
ffmpeg
go
htop
hugo
jq
libksba
libtool
libyaml
node
openssl@1.1
pkg-config
postgresql@14
python-typing-extensions
tldr
tree
yt-dlp
zlib

And now libpq is gone! Try out brew leaves yourself. You may be surprised at the amount of things installed that you may not actually need.

References

• https://docs.brew.sh/Manpage#leaves---installed-on-request---installed-as-dependency

]]> https://nelson.cloud/delete-all-node_modules-directories-recursively-in-macos-and-linux/?ref=rss Sun, 14 May 2023 00:00:00 +0000 https://nelson.cloud/delete-all-node_modules-directories-recursively-in-macos-and-linux/?ref=rss How to delete all node_modules directories recursively in macOS and Linux systems.We can use the find command to delete a specific directory recursively. This is the command formula:

1	find /path/to/starting/directory/ -type d -name "directory_to_delete" -exec rm -rf {} \;

For example, if we wanted to delete all node_modules directories within the path /projects/javascript/, we would run:

1	find /projects/javascript/ -type d -name "node_modules" -exec rm -rf {} \;

Note:

Sometimes the output says:

find: ./node_modules: No such file or directory

But the command should still work.

If you look closely, we’re really just executing a command against all node_modules directories in the /projects/javascript/ directory (rm -rf). This command can be modified to execute other commands against all node_modules directories, but that is out of the scope of this post :)

]]> https://nelson.cloud/how-to-install-older-versions-of-homebrew-packages/?ref=rss Tue, 18 Apr 2023 00:00:00 +0000 https://nelson.cloud/how-to-install-older-versions-of-homebrew-packages/?ref=rss How to install a specific version of Homebrew packages.

This method is outdated:

The approach outlined in this post still works in some cases, but as Homebrew has changed, this method has become unreliable. You may run into errors like:

Error: Couldn't find manifest matching bottle checksum.

Error: An exception occurred within a child process:
  NoMethodError: undefined method 'user' for nil

A cleaner approach is brew extract, which copies the historical formula into a local tap so Homebrew has the context it needs. See my newer post instead: How to Install a Specific Version of a Homebrew Package with brew extract.

It’s possible to install older versions of Homebrew packages by saving an older version of the corresponding Ruby file locally and running brew install <package>.rb. I’ll use the terraform package as an example.

tl;dr:

If I wanted to downgrade to Terraform 1.3.6, I would need to:

• Find the Ruby file for that specific version of Terraform on the Homebrew GitHub repo
• Download the Ruby file
• Uninstall the current version of terraform by running brew remove terraform
• Install the older version defined in the Ruby file by running HOMEBREW_DEVELOPER=true brew install --formulae terraform.rb

Let’s say we have terraform version 1.4.5 but we need terraform version 1.3.6. We can start by browsing to https://github.com/Homebrew/homebrew-core/tree/master/Formula and try to find the formula for terraform under the t directory.

Since there are a lot of files here, it’s easier to just modify the URL path in the browser. Modify the path based on the directory the command is in: Take the name of the package and append it at the end of the url, adding /<directory-containing-package>/<package-name>.rb to the URL. The .rb is important because all Homebrew packages are defined in Ruby (files with the .rb extension).

In this case, we’ll append /t/terraform.rb to the URL like so: https://github.com/Homebrew/homebrew-core/blob/master/Formula/t/terraform.rb

That URL will then take us to the Ruby file where the terraform Homebrew package is defined.

Next, click the “History” link on the upper right above the code, or just click on this link https://github.com/Homebrew/homebrew-core/commits/master/Formula/t/terraform.rb. In the next page, scroll down until you see the “terraform: update 1.3.6 bottle” link. Note that you may need to click on “Browse History” at the bottom of this page before continuing your search.

Click on the terraform: update 1.3.6 bottle link to see this page:

On the right side above the code block, click on the three dots, then click on “View file”.

This will take you to the package formula for this specific version of terraform.

On the upper right side of the code block, click on “Raw”. This gives us the exact code we need to install Terraform 1.3.6. Save the code locally to a file called terraform.rb. You can manually copy and paste or use curl:

1	curl https://raw.githubusercontent.com/Homebrew/homebrew-core/169f333f93fe0703b542cdf75b1decd4cb78f68d/Formula/terraform.rb > terraform.rb

Then, remove the existing package:

$ brew remove terraform

Uninstalling /usr/local/Cellar/terraform/1.4.5... (6 files, 69MB)

Then run brew install but specify the file you saved locally to install the older version. Note that as of Homebrew version 4.6.4 you can no longer install formulae directly from a file. You can get around this by specifying the environment variable HOMEBREW_DEVELOPER.

So to install Terraform from the file we just downloaded, run HOMEBREW_DEVELOPER=true brew install --formulae terraform.rb:

$ HOMEBREW_DEVELOPER=true brew install --formulae terraform.rb

==> Fetching downloads for: terraform
✔︎ Bottle Manifest terraform (1.3.6)
✔︎ Bottle terraform (1.3.6)
Warning: terraform 1.5.7 is available and more recent than version 1.3.6.
==> Pouring terraform--1.3.6.arm64_ventura.bottle.tar.gz
🍺  /opt/homebrew/Cellar/terraform/1.3.6: 7 files, 64MB
==> Running `brew cleanup terraform`...
Disable this behaviour by setting `HOMEBREW_NO_INSTALL_CLEANUP=1`.
Hide these hints with `HOMEBREW_NO_ENV_HINTS=1` (see `man brew`).

Now terraform version 1.3.6 is installed!

$ terraform version

Terraform v1.3.6
on darwin_arm64

Pro Tip:

You can pin the current version so it doesn’t upgrade in the future.

brew pin terraform

The next time you run brew upgrade it will be skipped:

$ brew upgrade

Warning: Not upgrading 1 pinned package:
terraform 1.5.7

When you’re ready to upgrade, you can unpin it:

brew unpin terraform

References

• https://docs.brew.sh/Manpage
• https://docs.brew.sh/FAQ#how-do-i-stop-certain-formulae-from-being-updated

]]> https://nelson.cloud/cleaning-up-residual-files-on-macos-after-deleting-apps/?ref=rss Sun, 28 Feb 2021 00:00:00 +0000 https://nelson.cloud/cleaning-up-residual-files-on-macos-after-deleting-apps/?ref=rss Clean up residual files and directories after deleting macOS apps.After deleting apps on macOS, they tend leave behind residual files and directories throughout the system. You can use the find command to find these files after an app has been deleted. I’ll be deleting the LastPass app and removing its residual files as an example.

2024-10-13 Update:

I recently discovered Pearcleaner. You can use this app to delete other apps along with all the extra files and folders they create. I recommend you use this first and then continue reading this post if you want to look more deeply.

You can download Pearcleaner from the link above or install it with Homebrew:

1	brew install --cask pearcleaner

Searching for Residual Files and Directories

To find directories and files related to LastPass, I ran a system-wide search using find. I excluded directories such as /System/Volumes/Data since those result in errors like “Operation not permitted”. I also excluded Homebrew directories that don’t need to be cleaned up. You can add more directories as needed, just make sure to not add a trailing slash to the filepaths!

1 2 3 4 5 6

find / \ -not \( -path /System/Volumes/Data -prune \) \ -not \( -path /usr/local/Homebrew -prune \) \ -not \( -path /usr/local/Cellar -prune \) \ -not \( -path /usr/local/Caskroom -prune \) \ -name \*lastpass\* 2>&1 | grep -v -E 'Operation not permitted|Permission denied|Not a directory'

The command may take some time to complete depending on your machine specs and amount of files you have. It took around ~10 minutes for me on a 2019 MacBook Pro with an i7 Intel CPU.

Here’s the output I got from the command above. I can now go through each of these files and folders and decide if I want to delete them manually:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

/private/var/folders/m9/_7bg6tbn3636m1zzlzq33bwh0000gn/T/com.lastpass.lastpassmacdesktop /private/var/folders/m9/_7bg6tbn3636m1zzlzq33bwh0000gn/C/com.lastpass.lastpassmacdesktop /Users/nelson/Library/Application Support/com.lastpass.lastpassmacdesktop /Users/nelson/Library/WebKit/com.lastpass.lastpassmacdesktop /Users/nelson/Library/Preferences/com.lastpass.lastpassmacdesktop.plist /Users/nelson/Library/Application Scripts/N24REP3BMN.lmi.lastpass.group /Users/nelson/Library/Application Scripts/com.lastpass.lastpassmacdesktop.safariext /Users/nelson/Library/HTTPStorages/com.lastpass.lastpassmacdesktop.binarycookies /Users/nelson/Library/HTTPStorages/com.lastpass.lastpassmacdesktop /Users/nelson/Library/Group Containers/N24REP3BMN.lmi.lastpass.group /Users/nelson/Library/Group Containers/N24REP3BMN.lmi.lastpass.group/Library/Preferences/N24REP3BMN.lmi.lastpass.group.plist /Users/nelson/Library/Group Containers/N24REP3BMN.lmi.lastpass.group/Library/Application Scripts/N24REP3BMN.lmi.lastpass.group /Users/nelson/Library/Containers/com.lastpass.LastPass /Users/nelson/Library/Containers/com.lastpass.lastpassmacdesktop.safariext /Users/nelson/Library/Containers/com.lastpass.lastpassmacdesktop.safariext/Data/Library/Application Scripts/com.lastpass.lastpassmacdesktop.safariext /Users/nelson/Library/Caches/com.crashlytics.data/com.lastpass.lastpassmacdesktop /Users/nelson/Library/Caches/Homebrew/Cask/lastpass--4.116.0.dmg /Users/nelson/Library/Caches/com.lastpass.lastpassmacdesktop

This could probably be automated all the way through the deletion step, but I prefer to double check what is actually going to be deleted.

Also, this may help to free up space on macOS, but I mainly did it because I like keeping my system tidy.

Try this out with whatever apps you’ve deleted in the past. You can also try finding files and folders be specifying a company name. For example, replace \*lastpass\* with \*microsoft\* and see what you get!

References

• https://stackoverflow.com/questions/4210042/how-do-i-exclude-a-directory-when-using-find

]]>