Wrote up how I manage dotfiles across macOS and Linux with Nix. One repo, one flake.lock — same shell, editor, and tools on every machine. Home Manager and nix-darwin do the heavy lifting.
Wrote up how I manage dotfiles across macOS and Linux with Nix. One repo, one flake.lock — same shell, editor, and tools on every machine. Home Manager and nix-darwin do the heavy lifting.
The first **Terminal Tuesday** is live! 🎉📢
We had Dolev Hadar showcase a super clean workflow built around **tmux + neovim + gh-dash**
▶️ Watch it here: https://www.youtube.com/watch?v=Q_-qOpwDBb0
💯 Lots of practical tips for improving Git/GitHub flow in the terminal!
👀 Wanna present your setup next? We're looking for guests!
#terminal #cli #tui #neovim #tmux #git #dotfiles #devtools #opensource
I Audited My Dotfiles and Found 30 Bugs
https://rant.mvh.dev/i-audited-my-dotfiles-and-found-30-bugs/
#dotfiles #chezmoi #1password #git #templates #zsh #developertools
Managing Dotfiles with Chezmoi Part 2: Secrets, Aliases, and Template Patterns
https://rant.mvh.dev/managing-dotfiles-with-chezmoi-part-2-secrets-aliases-and-template-patterns/
#dotfiles #chezmoi #1password #git #templates #zsh #developertools
Managing Dotfiles with Chezmoi: Part 1 - The Foundation
https://rant.mvh.dev/managing-dotfiles-with-chezmoi-part-1-the-foundation/
#dotfiles #chezmoi #zsh #automation #developertools #macos #linux #homebrew
I love Bash. I used to write tons of Bash. There is a lot of Bash in my life, even to this day.
But here's my life now:
* Bash holds some stuff together (small stuff: usually setting variables, aliases, and/or piping together a few CLI tools. See https://github.com/wolf/dotfiles/tree/main/shells/dot-config/shells/topics for examples)
* Zsh is good at doing stuff when I type, so that's my login shell
* If I have to do something interesting, why not just a Python script? In modern times, with a `uv` shebang line and self-specified dependencies ... the only externally visible additional requirement is `uv` itself (you don't even need Python). Just like a shell-based answer: you end up with a single stand-alone file
I'm not going to argue about "but you have to install `uv`". You do you.
I'm launching "**Terminal Tuesdays**" 🖥️
🐁 A biweekly meetup where someone from the community showcases their terminal setup.
💯 Configs, TUIs, scripts, weird hacks
📡 Join our Discord: https://discord.com/invite/6EUERBrAMs
▶️ Going to be recorded & published: https://youtube.com/@terminalcollectiveorg
dotGit — minimal dotfiles manager built on a bare git repo + shell aliases.
What I use most: `.gg PATH` greps all tracked dotfiles and takes you to the line. `.ge zshrc` fuzzy-finds a filename with preview and opens in $EDITOR.
No symlinks or extra tooling. Files stay exactly where they are.
🔗 https://code.opennomad.com/opennomad/dotGit
(mirrors: https://codeberg.org/opennomad/dotGit · https://github.com/opennomad/dotGit)
#linux #dotfiles #bash #git #selfhosted #opensource #commandline
New blog post! My dotfiles repo evolved from basic shell configs to managing my AI coding agents — Claude Code and OpenCode get the same instructions, exclusions, and skills through symlinks.
If you're using AI coding tools regularly, version controlling their configs is a game changer.
Just published follow-symlink - a tiny Linux daemon that watches directories auto-updates symlinks when the target folder is moved using inotify
Every existing tool (GNU Stow, chezmoi, watchman) requires you to manually re-run something after reorganising. This fills that gap with an event-driven approach.
→ https://github.com/JaPossert/follow-symlink
PR or info that this has been done before (more elegantly), welcome 🙏