alt Hacker NewsAs a counterpoint, one of the most useful customizations I've made to my prompt is to emit the exit status of the prior command. Knowing that something failed is a useful signal, esp. when sometimes the thing failing just fails to emit any output that indicates that it failed.
I only emit it if the prior command fails, too, so it doesn't clutter things the 90% of the time things are working.
» true
» false
(last command returned 1.)
»
It's also useful the other way: when a program emits and error and exits with "success".
Replies
Oh, how do you automate that? I usually add a "& say done | say failed" to long-running tasks if I remember to do it.
I like the exit code feature a lot; Starship does that with my config in a subtle color change.
My shell customization is largely throwing Starship in (so it looks the same on all the machines I use -- Ubuntu servers at work, macOS at home, nixOS/Fedora/etc. servers for personal use.) and a starship.toml I wrote once and now leave alone.
That's useful indeed. Did you custom-code it, or is it e.g. an ohmyzsh plugin or something?
This and command duration if the command ran longer than 10 seconds are the most useful things to add.