Assuming I have different personal and work git server hosts, I have pre-commit and post-checkout hooks which automate most of this like so:

...
ORIGIN="$(git remote get-url origin 2>/dev/null)"
if expr "$ORIGIN" : '.*megacorp\.com' > /dev/null ; then
    # Setting repo email to work email
    git config --local user.name 'Worker Drone'
    git config --local user.email 'workerdrone@megacorp.com'
else
    # Setting repo config to personal email
    git config --local user.name 'Personal User'
    git config --local user.email 'personal@home.com'
fi
...

I tried to switch back using the nightly channel. Loved it for a few days when it would start up in under a minute with a couple of thousand tabs open (but not loaded). Then after a few days it started leaking memory and filling up the whole disk in a few minutes causing forced reboots.

I use zaw’s zaw-history for Ctrl+r instead of fzf but I like the command bookmarking feature of hstr as I find myself hunting for old crafted commandlines from time to time. Maybe I’ll steal it for zaw!

I first saw this article here https://sentinelone.com/blogs/shut-snitch-reverse-engineering-exploiting-critical-little-snitch-vulnerability-reverse-engineering-mac-os-x/ . Where did it actually originate?

EDIT: Seems reverse.put.as is the actual site of gdbinit on github.com, the author of the article. Wonder if they are connected to sentinelone.com somehow or if sentinelone is just presenting the article as their own…

I am wondering if we need a separate tag for ads too as privacy may not be a great fit. On the other hand people might start to use it to point at ads themselves rather than on content about intrusive advertisements, adbusting, ads using personal data (thought that would fit into privacy) etc.

I was expecting to get something back for sys.exit as it mentions python but I don’t get any results back.

It would be nice if the same energy went into submitting patches to the owners of the man pages to improve their EXAMPLES sections.

Could be a free Dash for Mac replacement but the implementation is very buggy or unintuitive at the moment. Selection (eg python subset) doesn’t seem to persist or even trigger consistently. But it is open source so possible to figure out and fix the issues by spending some time.