michaelallen

Will do. I'll add the ability to change the prefix/suffix.

Thanks :-) It's just something I've been using for a while so very tailored to my needs. YMMV.

Thanks! Glad you like it.

Fair point on the `git:(`, it's mostly a hold over from robbyrussells oh-my-zsh theme (which inspired me to make the first version of this about 2 years ago (https://github.com/michaeldfallen/oh-my-zsh/blob/master/them...).

The entire thing is composable so if you want a prompt without those bits just fork and modify: https://github.com/michaeldfallen/git-radar/blob/master/prom....

Or should I be making these "pieces" like `git:(` and `)` configurable through args / env vars?

On the untracked files I personally never leave a file untracked. I either commit it or add it to .gitignore. Though I see how you use git differently, how about a --ignore-untracked to ignore untracked files?

I did try that on a previous tool Butler (https://github.com/michaeldfallen/butler) but I found that some shells don't actually set `$SHELL`.

"But that would take local governments to sign up and developers / designers to begin solving problems that matter to their local society. Might be worth a shot though?"

Tech minds are always want to build a tool, not sure why it's just how we're wired.

Don't.

Just do less and do something.

Ask the "Head of Social Service & Care" you were talking to to get 5 or 10 colleagues to get in a room with yourself and a few other hackers.

Ask them their problems and write it all down. Then build something to solve ONE of their problems. This could be as boring as reducing their wasted time and money by automating a menial task in the departments offices.

Once you've built a thing show them it, then ask them to organise another meeting to talk about other problems. Ask them to invite community members. Then you do it again, and again.

Helping people isn't about building things, it's about talking to them about their problems and solving them. Keyword there "talking".