Since a couple of weeks, however, I started replacing small menu bar utilities with Hammerspoon. So, I thought, can I replace Lolgato with pure Hammerspoon?
Turns out you can (with some help from Claude Code). The result is a new Spoon, for which I opened a PR to the Spoons repository.
The other day, I stumbled upon the GNOME-only app Hieroglyphic, that finds LaTeX and typst symbols when you draw them on a canvas.
So, I set out to port it to macOS and I can happily report that I succeeded. There’s a PR open to contribute everything back, but in the meantime, grab it from my GitHub fork!
Since having a notch on my MacBook, I cannot fit all the icons in my menu bar.
I’ve tried heaps of apps to make it work: Bartender, Ice/Thaw, and Hidden, but they all had subtle bugs.
Turns out, there’s an easy way to avoid using these apps by shrinking the spacing and padding of the menu bar items, and now I don’t need any of these apps!
Recently, Michael Lopp wrote I Hate Fish in which he outlined his approach to getting work done.
The simplicity to remember when to do what resembles how I use Things (which he also uses) in combination with Mailmate and Keyboard Maestro:
When an email requires follow-up, I hit ⌃ ⌥ ⇧ ⌘ R and I type in how many days I want to be reminded.
Keyboard Maestro asking me in how many days I should be reminded
The subject is then copied and becomes the title of the item. A clickable link to the email is added as a note.
The item in Things
That’s it. On the day I have to follow-up, the item will pop up in my Things list.
The system also works when I just replied to an email, and I want to be reminded if there has been a follow-up or not.
The core of the system relies on this Keyboard Maestro macro
The Keyboard Maestro macro
Slack’s /feedcommand is really useful; it allows you to subscribe to an XML feed and receive updates in any channel.
However, it doesn’t always work as expected, and when it fails, there’s no way to find out why.
Recently, I added an Atom feed to an announcement channel, but the posts weren’t coming through. I initially thought the /feed functionality might be incompatible with announcement channels, but I was wrong.
After contacting support, they told me:
We only recognise the following tags for date values: <pubDate>, <issued>, <modified>, <updated>, <dc:date>, or <published> (this last date type applies to Atom feeds) and the date tag fields must be within an <item> tag to be read
Great, I thought. Since I controlled the Atom feed, I figured I could just wrap every entry in an <item> tag. However, the Atom standard expects items to be wrapped in <entry> instead. The spec says feeds should be like: