I was working with a babashka file which spits out an HTML file when I evaluate it and since babashka can also easily run shell commands, I figured I could just add these two lines at the bottom of my nrepl-connected script:
(defonce browser-window (:out (shell/sh "xdotool" "selectwindow"))) (shell/sh "xdotool" "key" "--window" browser-window "F5")
The first time it's evaluated, I can use the mouse to select the desired window and from then on that window will be reloaded every time I evaluate the file. There's a bit of a limitation in that it doesn't care what the current browser tab is, it just triggers whatever is currently selected, but it's good enough for my purposes.
Job done! Well, not quite.
Of course this doesn't automate the reload when tweaking the CSS file. And it would be nice to have that functionality when working on this site. Really, I need a file watcher, and happily there's a babashka pod for file watching1. Hooking it up is straightforward, but when there's dozens or even hundreds of file changes, it gets a bit manic, so I hacked up together a debouncer using a cancellable future in an atom 2:
(def reload-op (atom nil)) (defn trigger-reload  (let [[old _] (reset-vals! reload-op (future (Thread/sleep 20) (reload)))] (when old (future-cancel old))))
I also used the same mechanism to implement a
watch command for this site which triggers a re-render whenever a file changes. Combined with the browser reload script watching the output folder, it makes for a nice workflow.
The full script is available as a gist and requires babashka and xdotool to be installed. I ended up also making a macOS version that makes use of AppleScript to trigger the reload instead. If you're reading this, I hope you find it useful.
- Well, there's two.↩
- I got some advice on how to improve it from the clojurians slack, some of which I even applied, though I can't apply it all now because of a current limitation in babashka. I did learn about
reset-vals!which is better than accessing the atom to cancel it and then calling
reset!. Some also suggested an approach using core.async which sounds cool but maybe overkill for this particular hack.↩