Well, bash should show up quickly enough. But yeah.
I’m also no longer much of a bash guy. Back when I was my scripts were a lot simpler, and broke in weird ways a lot more. And every time I picked up a new defensive habit, my bash became a little bit uglier, and I thought to myself “maybe I should just do this in Python”.
But this script would be a lot longer in Python.
IME I’ll rather find some openapi docs for Google than their actual product docs. As in, I’ll start out trying to read their kubernetes docs, then shortly after it’s “fuck it, I’m going to docs.rs/k8s-openapi”.
My actual worst case are Elastic’s docs, though. Somehow they have plenty of stuff in there, just never the stuff I’m trying to figure out.
For those who want to give it a go:
#!/bin/bash
set -euo pipefail
while read -rd ":" path
do
for bin in "$path"/*
do
# don't error out if there's no manpage
set +e
man "$(basename "$bin")"
set -e
done
done < <(printf '%s%s' "$PATH" ":")
when you get sick of it, hit ^Z (ctrl-z) and go kill %1. Then you get to start all over from the start next time!
Bonus points for starting a tracker so you can count how long it takes to go from “eugh, what’s with that overwrought and excessively defensive bash script” to “fuck, now I’m doing it too”
Nah. If we take the US as an example they have rampant NIMBYism, a suburbanism ideology that isn’t sustainable financially (or ecologically or socially, for that matter), and rather strict zoning, with the worst stemming from the city of Euclid, and thus being named “euclidean zoning”.
If you’re up for some videos, then StrongTowns, CityNerd and NotJustBikes all talk about this at length.
No, but the weirdos who insist on spelling it “SystemD” always seem to hate systemd.
systemd is pretty great. I tend to start long-running processes as user services, and I’ve even taken to starting some apps that give an old laptop trouble with
systemd-runand a slice with some memory restrictions. Easy peasy, works great, all declarative, no wibbly-wobbly shell scripts involved.