med
Only leftists bother to separate communist and Marxist
Thanks for the feedback - It was a systemd issue. Something caused it to continue generating slices for espanso until the machine locked up - probably spawned with each terminal. It happened on out of date fedora install 36 (when 41 was out) with gnome on it.
Since then I've moved to a window manager for all my machines and would likely invoke it the same way - perhaps now it's time to revisit!
I used eapanso for a few years, but kept running in to issues with it spawning hundreds of versions of itself.
I really miss it though. Would you say it has matured?
We're everywhere!
Strimmer out here in Bermuda too
Ctrl +a and Ctrl +e for beginning and end of line are from Emacs.
GNU Readline is what provides them in the bash. There's a bunch of shortcuts worth learning in there!
Most distributions I've tried use Emacs as the default shell binding style, some of the bindings are even available in things like appliance cli's like Cisco IOS and clones.
Bash supports vi mode too, you just have to switch to it.
set -o vi
ZSH uses zle (ZSH Line Editor) instead of Readline, but I assume the Emacs style bindings have been copied over to zle for muscle memory portability. You can switch the keymap in zle,
bindkey -v
Yes. But also, despite having done it literally thousands of times, I still can't tell you which way round to put the target and the link name for a softlink on the first go.
My first guess is always
ln -s $NAME $TARGET
No amount of repetition will fix this.
Sounds like you have reason to bump it up the list now - two birds with one stone.
I need to do this too. I know I have stuff deployed that has plaintext secrets in .env or even the compose. I'll never get time to audit everything. So the more I make the baseline deployment safe, the better.
Well, apparently Meta's pixel tracking script was bypassing that VM and SELinux enforcment to exfil tracking impressions for years and doing it by creating webRTC dummy ports, that were chatting with their own apps (Instagram, Facebook, ?WhatsApp?-not sure). So not sure this was a great implementation to begin with.
And this was working despite sandboxing on other browsers
Source: https://arstechnica.com/security/2025/06/meta-and-yandex-are-de-anonymizing-android-users-web-browsing-identifiers/