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/proper-hugo-template-syntax-highlighting-with-go-html-template/?ref=rss Sun, 03 Aug 2025 00:00:00 +0000 https://nelson.cloud/proper-hugo-template-syntax-highlighting-with-go-html-template/?ref=rss Improve Hugo template code highlighting using go-html-template Markdown code blocks.I recently learned that you can highlight Hugo template code blocks by specifying go-html-template after the opening backticks.

So the opening backticks in a Markdown file look like this:

```go-html-template

It makes a huge difference when highlighting Hugo template code blocks. I was previously using html for syntax highlighting and it wasn’t as good.

For example, here is some HTML + Hugo templating stuff being highlighted with html:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

{{- define "main" }} {{- if .Title }} <header class="page-header"> <h1>{{ .Title }}</h1> {{- if .Description }} <div class="post-description"> {{ .Description }} </div> {{- end }} </header> {{- end }} <ul class="terms-tags"> {{- $type := .Type }} {{- range $key, $value := .Data.Terms.Alphabetical }} {{- $name := .Name }} {{- $count := .Count }} {{- with site.GetPage (printf "/%s/%s" $type $name) }} <li> <a href="{{ .Permalink }}">{{ .Name }}<sup> {{ $count }}</sup></a> </li> {{- end }} {{- end }} </ul> {{- end }}{{/* end main */ -}}

Here’s the same code block but with go-html-template specified:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

{{- define "main" }} {{- if .Title }} <header class="page-header"> <h1>{{ .Title }}</h1> {{- if .Description }} <div class="post-description"> {{ .Description }} </div> {{- end }} </header> {{- end }} <ul class="terms-tags"> {{- $type := .Type }} {{- range $key, $value := .Data.Terms.Alphabetical }} {{- $name := .Name }} {{- $count := .Count }} {{- with site.GetPage (printf "/%s/%s" $type $name) }} <li> <a href="{{ .Permalink }}">{{ .Name }}<sup> {{ $count }}</sup></a> </li> {{- end }} {{- end }} </ul> {{- end }}{{/* end main */ -}}

Big difference!

Note that I’m using Chroma for syntax highlighting so your experience may vary, but Chroma comes by default with Hugo.

References

• https://gohugo.io/content-management/syntax-highlighting/
• https://github.com/alecthomas/chroma

]]> https://nelson.cloud/a-trick-to-remove-unwanted-whitespace-after-links-in-hugo/?ref=rss Fri, 11 Jul 2025 00:00:00 +0000 https://nelson.cloud/a-trick-to-remove-unwanted-whitespace-after-links-in-hugo/?ref=rss Use this template syntax to remove unwanted whitespace after links in Hugo.

tl;dr:

You can use the {{- "" -}} template syntax to remove trailing whitespace on links in Hugo.

For some reason, Hugo was rendering links with a space after them. Here’s a screenshot of what that looked like:

It’s subtle but becomes more obvious and distracting in link-heavy pages.

Here is the markdown that I was using to generate the link above. Nothing out of the ordinary:

1	This sentence has a [link at the end](https://example.com).

In Hugo, you can apply post-processing to links through link render hooks by editing the layouts/_default/_markup/render-link.html file. Here’s my terrible template that I use to process links. Once again, nothing stood out that would add unnecessary whitespace after links:

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

{{- $url := .Destination -}} {{- $refParam := "" -}} {{- $refDomain:= "" -}} {{- $hasQuery := strings.Contains $url "?" -}} {{- $hasHash := strings.Contains $url "#" -}} {{- if $hasQuery -}} {{/* taking into account existing query strings */}} {{- $refParam = "&ref=" -}} {{- $refDomain = "nelson.cloud" -}} {{- else if $hasHash -}} {{/* ensuring that URL doesn't have a hash # */}} {{/* do nothing in this case */}} {{- else -}} {{- $refParam = "?ref=" -}} {{- $refDomain = "nelson.cloud" -}} {{- end -}} <a href="{{ .Destination | safeURL }}{{ $refParam }}{{ $refDomain }}"{{ with .Title}} title="{{ . }}"{{ end }}{{ if strings.HasPrefix .Destination "http" }} target="_blank" rel="noopener noreferrer"{{ end }}>{{ .Text | safeHTML }}</a>

Here is the HTML that was generated by Hugo based on the Markdown I wrote and the processing in render-link.html. This is straight from the browser dev tools:

The period was on its own line, which looks suspicious. Why is there additional space being added though? I tried modifying my CSS, my Markdown, and render-link.html to see if I could remove the whitespace but nothing worked.

Eventually, I was out of ideas and asked ChatGPT what could be going wrong. ChatGPT suggested I could add the {{- "" -}} template syntax to render-link.html to remove the whitespace. Apparently that would force the removal of both leading and trailing whitespace. And sure enough it worked!

I modified my render-link.html template to include the {{- "" -}} template syntax at the end of the <a> tag in the highlighted line:

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

{{- $url := .Destination -}} {{- $refParam := "" -}} {{- $refDomain:= "" -}} {{- $hasQuery := strings.Contains $url "?" -}} {{- $hasHash := strings.Contains $url "#" -}} {{- if $hasQuery -}} {{/* taking into account existing query strings */}} {{- $refParam = "&ref=" -}} {{- $refDomain = "nelson.cloud" -}} {{- else if $hasHash -}} {{/* ensuring that URL doesn't have a hash # */}} {{/* do nothing in this case */}} {{- else -}} {{- $refParam = "?ref=" -}} {{- $refDomain = "nelson.cloud" -}} {{- end -}} <a href="{{ .Destination | safeURL }}{{ $refParam }}{{ $refDomain }}"{{ with .Title}} title="{{ . }}"{{ end }}{{ if strings.HasPrefix .Destination "http" }} target="_blank" rel="noopener noreferrer"{{ end }}>{{ .Text | safeHTML }}</a>{{- "" -}}

Then my links were rendering without additional space after them, and here’s a screenshot showing that:

The weird thing is that when I checked the HTML being generated, it looked identical to the original before I added the template syntax and I had no idea why:

But at least the whitespace was gone when viewing the article in a browser. That’s what matters.

This template syntax trick can probably be applied to other areas of Hugo and not just for links, but I haven’t done any additional experimenting.

References

• Wherever ChatGPT stole got this information from. I feel weird using ChatGPT as a reference but that really is how I discovered the solution.

]]> https://nelson.cloud/remove-unnecessary-hugo-meta-tag-to-keep-html-lean/?ref=rss Sun, 15 Jun 2025 00:00:00 +0000 https://nelson.cloud/remove-unnecessary-hugo-meta-tag-to-keep-html-lean/?ref=rss Remove an unnecessary and auto-generated Hugo meta tag by setting <code>disableHugoGeneratorInject</code> to <code>true</code>.I like to keep my Hugo site as lean as possible for performance reasons and to save on hosting costs.

I recently discovered that Hugo generates an HTML <meta> tag with the Hugo version in the <head> tag. This is done by default and looks like this:

1 2 3

<head> <meta name=generator content="Hugo 0.146.2"> </head>

To remove this tag, we can disable it in config.yaml or config.toml by setting the disableHugoGeneratorInject boolean to true.

In YAML:

1	disableHugoGeneratorInject: true

In TOML:

1	disableHugoGeneratorInject = true

If setting disableHugoGeneratorInject doesn’t work, do a global search in your Hugo project for {{ hugo.Generator }}. This template syntax outputs the same <meta> tag and doesn’t respect the disableHugoGeneratorInject configuration (at least as of Hugo v0.147.8).

References

• https://gohugo.io/configuration/all/#disablehugogeneratorinject
• https://gohugo.io/functions/hugo/generator/

]]> https://nelson.cloud/how-to-generate-and-format-the-current-date-and-time-in-hugo-with-dateformat/?ref=rss Sun, 22 Dec 2024 00:00:00 +0000 https://nelson.cloud/how-to-generate-and-format-the-current-date-and-time-in-hugo-with-dateformat/?ref=rss Several examples of dateFormat including date only, date + 12-hour time, date + 24-hour time, date + timezone, and date + UTC offset.Here are a bunch of Hugo snippets you can use to generate the current date and time in your Hugo site.

You can copy and paste these into HTML templates. If you want to use these within your posts/articles (Markdown files) you’ll need to create a shortcode first. Scroll down to the Using Shortcodes section for more details.

I’m running Hugo v0.140.0+extended.

For all examples, I will assume the time is 2024-12-22 2:30PM PT.

Date Only

1	{{ now | dateFormat "2006-01-02" }}

Output:

2024-12-22

Date and 12-Hour Time

1	{{ now | dateFormat "2006-01-02 3:04" }}

Output:

2024-12-22 2:30

You can specify AM or PM by adding PM to the time. Go will output the correct one (AM/PM) based on the actual time:

1	{{ now | dateFormat "2006-01-02 3:04PM" }}

Output:

2024-12-22 2:30PM

Note:

Always use PM (or pm) as the placeholder in the time string. Using AM in the time string will print the literal text AM as regardless of the actual time. For example:

1	{{ now | dateFormat "2006-01-02 3:04AM" }}

Will output:

2024-12-22 2:30AM

Even if it’s actually 2:30PM.

Date and 24-Hour Time

Essentially just changing 3:04 to 15:04.

1	{{ now | dateFormat "2006-01-02 15:04" }}

Output:

2024-12-22 14:30

Date and Time with Timezone

1	{{ now | dateFormat "2006-01-02 15:04 PST" }}

Output:

2024-12-22 14:30 PST

It’s possible to add just about anything in place of the timezone and it’ll take it. You can even add text that isn’t a valid timezone.

1	{{ now | dateFormat "2006-01-02 15:04 test" }}

Output:

2024-12-22 14:30 test

Date, Time, Timezone, and UTC Offset

There are two ways that I found of doing this.

The first way:

1	{{ now | dateFormat "2006-01-02 15:04 PST -0700" }}

Output. Note how Hugo changed the offset from -0700 to -0800 in this case:

2024-12-22 14:30 PST -0800

The second way:

1	{{ now | dateFormat "2006-01-02 15:04 PST UTC-0700" }}

Output. Hugo once again changed the offset from UTC-0700 to UTC-0800:

2024-12-22 14:30 PST UTC-0800

Timezones and CI/CD

These snippets work for your current timezone but if you use a CI/CD solution you may need to specify the timezone through an environment variable or etc. It depends on your CI/CD solution. I couldn’t find a way to set the timezone in Hugo itself so I don’t think it’s possible.

Using Shortcodes

These snippets can be copied and pasted into .html templates. However, to use them in Markdown files, you’ll need to create a separate file in layouts/shortcodes/ and then use that shortcode in a markdown file.

For example, I can create a file generate_date.html in layouts/shortcodes/ with the following contents:

1	{{ now | dateFormat "2006-01-02" }}

Then I can reference this shortcode in a markdown file with this syntax:

1	{{< generate_date >}}

An example along with some other markdown:

1 2 3 4 5

# A Header in Markdown Some text in markdown *The current date is*: {{< generate_date >}}

References

• https://discourse.gohugo.io/t/how-to-display-time-by-timezone/42643/7
• https://community.cloudflare.com/t/hugo-timezone-format-issue/390678

]]>