// the find
fatih/dotfiles
My personal dotfiles
The author's personal dotfiles: fish, Neovim, tmux, Ghostty, git, and keyboard firmware configs for several split keyboards, all placed by a Makefile. It is written for one person's macOS setup, so it works best as a reference to read and copy from, not something to install as-is.
- Keyboard firmware lives in the same repo as the shell config: ZMK for the Glove80, QMK for the Advantage 2 and Mode Encore, each with its own readme. That is rare to find in one place, and the keymaps are a useful reference if you're in that niche.
- Light and dark tmux themes are separate files (tmux-dark.conf, tmux-light.conf) rather than one file full of conditionals, which makes each theme easy to read and change.
- Each fish function is a small file of its own (ghpr.fish, copy_branch.fish, gp.fish), so each one can be read, copied, or deleted without touching the rest.
- The Brewfile and Makefile make the setup reproducible, so most of a new machine's configuration comes from one `make` run and the repo doesn't need to be reconstructed by hand.
- It is hardcoded for one macOS setup. `chsh -s /usr/local/bin/fish` assumes the Intel Homebrew prefix, which Apple Silicon Macs don't use (/opt/homebrew), and the `defaults write` line is macOS-only. Anything else needs editing before it runs on another machine.
- The new-machine steps are only partly automated. The SSH key, default shell, first Neovim launch, and font setting are manual, and the README doesn't say what `make` does to files that already exist in the home directory.
- The README points to `qmk/halcyon-elora/readme.md`, but the repo tree lists the directory as `qmk/halycon-elora`. The path as written doesn't exist.
- Adopting it means forking. The README says it is personal and that PRs changing the workflow may be refused, so you would be maintaining your own copy of someone else's preferences.