From 98d0debb43e0c807cf753b20f74ec1a2d2a327c2 Mon Sep 17 00:00:00 2001 From: Firehose Bot Date: Sun, 28 Jun 2026 10:16:02 +0200 Subject: [PATCH] add file location --- AGENTS.md | 3 +++ .../2026/06-26-an-example-would-be-handy-right-now.md | 4 ++++ 2 files changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 54d4d4d..879a937 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -3,6 +3,9 @@ This project has a *zero defects policy*. When you are unsure about something, ALWAYS ask the user. + +You run in a `nono` sandbox. Always ask the user to run commands that require privilege, like docker, sudo or package installation. + # Repository structure This is an Elixir monorepo with two parts: diff --git a/app/priv/blog/engineering/2026/06-26-an-example-would-be-handy-right-now.md b/app/priv/blog/engineering/2026/06-26-an-example-would-be-handy-right-now.md index 8ddf7c3..e9ecb96 100644 --- a/app/priv/blog/engineering/2026/06-26-an-example-would-be-handy-right-now.md +++ b/app/priv/blog/engineering/2026/06-26-an-example-would-be-handy-right-now.md @@ -94,3 +94,7 @@ Some of my blogposts seem to help other people, which was the stated aim, and it [Backing up your work to the internet](https://lkml.iu.edu/hypermail/linux/kernel/9607.2/0292.html) is great. I hope you enjoyed this yak shaving adventure. The rabbit hole of emacs is deep, but removing friction from my workflows is not that onerous. And I needed to tinker with a small bit of code to recover from developing a more conceptual talk and a new workshop. + +# Where is the code? + +I forgot about that the first time around. For now it lives in [init.el](https://gitea.apps.sustainabledelivery.com/mostalive/firehose/src/branch/main/init.el) in the firehose repository. I want it to load when I open a markdown file in the repository. So it works on my other machines, and in the unlikely event that someone else uses firehose for their blog and uses Emacs to write posts, they should have the code to enjoy images too.