The requirement I had was to be able to open macOS Finder in the folder of the file that I was currently editing. I use this a lot when writing posts for dx13. As images live in the same folder on disk as the post they are used in, it’s useful to be able to quickly flick to the folder and drop an image there for use in a post.

The code itself is pretty simple. I’ll put it here. If you are here just for the code, you can grab it and be on your way. Put this code anywhere in your config:

vim.api.nvim_create_user_command('Rfinder',
    function()
        local path = vim.api.nvim_buf_get_name(0)
        os.execute('open -R ' .. path)
    end,
    {}
)

The interesting part is the story of how I got to the code. Exposing this functionality in Neovim was a small epiphany for me in understanding how vim is different from VS Code, my previous editor:

While Neovim is a powerful editor of itself, configuring it isn’t selecting from a static set of choices, as with VS Code, but instead a way of evolving the editor’s functionality to meet your needs. Adding small bits of function in that configuration is completely normal, unlike in VS Code where an extension is needed.

Perhaps reading through my thought processes will help this click for someone else starting out (for a second time, in my case!) with Neovim.

One of the things I’d not really considered about the crypto-mining craze of the last few years was its out-sized effect on the market for components:

One of the perks of normality largely returning to the PC components market now that the crypto mining bubble has popped has been a big improvement in component availability. Video cards were of course the biggest change there – even if prices on the latest generation remain higher than many would like to see – but crypto farms were also soaking up everything from CPUs and RAM to power supplies.

It’s obvious once you’ve been told about it. It’s fascinating to think of the sheer quantity of parts that these mining operations would’ve required. It’s depressing too, given the vacuousness of the market.

I wonder whether the new craze in AI model training will soak all these components back up again.

Via Anandtech.

I used Vim for several years, albeit at a rather shallow level of skill. I stopped about ten years ago, for one reason or another. Still, I kept a candle burning for Vim. There was just something about it. And so it wasn’t hard to be tempted when I was told that it had improved a lot in the time I’d been away.

And, oh my, it has. There’s everything I loved, still there. The weird but lovely modal editing. The speed, oh goodness the speed. But also Vim now has the things I left Vim to search for. Smart completion and navigation. Code refactorings. Pop up documentation. Clever highlighting. A scripting language I can understand.

There are so many truisms in The Grug Brained Developer. I enjoyed it immensely; the writing is somehow so, so apt for its subject. So many clubbable grugs. Including myself, of course, but I think I’ve learned.

complexity is spirit demon that enter codebase through well-meaning but ultimately very clubbable non grug-brain developers and project managers who not fear complexity spirit demon or even know about sometime

one day code base understandable and grug can get work done, everything good!

next day impossible: complexity demon spirit has entered code and very dangerous situation!

We have a big rosemary bush in our back garden. The bees love it. A sure sign of spring having sprung is the buzzing from the rosemary.