Dotfiles

My personal dotfiles, managed with GNU Stow. The repo is split into three stow packages so macOS and Linux machines share what they can:

Package	Contents
shared/	bash, git, nvim, ghostty, ansible, Claude, portable scripts
macos/	Hammerspoon, LaunchAgents, gnupg (PCSC), brew packages, scripts
linux/	Linux-only shell setup (grows as needed)

Files are stowed with per-file symlinks (--no-folding) so app state written next to stowed files never leaks into the repo. README.md and setup_machine.sh live outside the packages and are never stowed.

The shared .bashrc sources ~/.config/bash/os.sh, which the macos and linux packages each provide their own version of — OS-specific shell setup goes in there, not in the shared file.

New machine setup — macOS

1. Clone the repo to the home folder:

   git clone ssh://git@forge.quinlan.cloud:2222/joshquinlan/dotfiles.git ~/.dotfiles
   

2. Run ~/.dotfiles/setup_machine.sh. It is idempotent and handles:

   • Homebrew (installs if missing, works on Apple Silicon and Intel)
   • Stowing shared + macos into $HOME (--adopt means the repo always wins over any pre-existing files)
   • All packages, via get_packages.sh
   • macOS defaults (Hammerspoon config location)
   • Homebrew bash as the login shell
   • TouchID for sudo (/etc/pam.d/sudo_local)

3. Open Neovim once — lazy.nvim installs itself and all plugins on first launch. Versions are pinned in lazy-lock.json.

New machine setup — Linux

No setup script yet (write one once the distro is known). Manually:

git clone ssh://git@forge.quinlan.cloud:2222/joshquinlan/dotfiles.git ~/.dotfiles
~/.dotfiles/shared/.local/bin/restow --adopt && git -C ~/.dotfiles checkout .

Then install the tools the configs expect: stow, nvim, lsd, most, gpg, gpg-tui, fzf, fd, termscp, and anything else the shell complains about. For ble.sh, either use the distro package or extract the prebuilt nightly tarball to ~/.local/share/blesh (see setup_machine.sh for the exact command; the bashrc also checks /usr/share/blesh).

Day-to-day

• After adding or removing files in the repo, run restow — it stows shared plus the right OS package automatically. restow -n for a dry run; extra flags pass through to stow.

• New files go in the most specific package that fits: shared unless it genuinely only makes sense on one OS.

Colour schemes

One palette rules every themed tool. The source of truth is shared/.config/themes/kanagawa.sh (hex values plus curated 256-colour approximations):

• Runtime consumers (fzf, ble.sh) read the THEME_* variables directly; .bashrc sources the palette early.
• File-based configs (lsd, termscp, urlscan, the Ghostty cursor shader) are rendered from shared/.config/themes/templates/ by running gen-theme. The generated files carry a GENERATED header and are committed; edit the template or the palette, never the output, then rerun gen-theme (needs envsubst, from the gettext package).

A new scheme is a new palette file defining the same variable set: source it from .bashrc and run gen-theme <name>.

Git identity

• Default identity is Josh Quinlan <josh@quinlan.cloud>.
• Repos with GitHub, GitLab, or sr.ht remotes automatically switch to the donquinleone identity via includeIf → priv.inc.

Gotcha: the global git config is itself a stowed file in this repo. Rebasing here checks out old commits, which silently reverts the global config mid-rebase (identity, signing key, everything). When rewriting history in this repo, set the identity explicitly:

GIT_COMMITTER_NAME="Josh Quinlan" GIT_COMMITTER_EMAIL="josh@quinlan.cloud" \
  git commit --amend ...

macOS Gatekeeper

Some apps refuse to open, claiming to be "damaged". That's Gatekeeper. Fix per app with:

xattr -cr /Applications/AppName.app