summaryrefslogtreecommitdiff
path: root/CLAUDE.md
AgeCommit message (Collapse)Author
2026-09-21hammerspoon, ghostty: example files for their machine-local configsIgor Soarez
ssh and git each ship one; these two hooks were discoverable only by reading the config that loads them. Both examples carry what is easy to get wrong: init.lua's hotkey() helper and mod tables are locals, so a local.lua calls hs.hotkey.bind directly, and a binding there can only be shadowed, never deleted; in Ghostty a single-value key replaces while keybind accumulates, and `ignore` is how a binding is switched off rather than added to. Checked rather than assumed: the lua parses, and the Ghostty example validates and, dropped in as ~/.config/ghostty-local, does what it says -- font-size, command and background-opacity replaced, super+shift+n added, alt+enter turned off.
2026-09-21CLAUDE.md: where a single machine's changes go, and what to do without a hookIgor Soarez
The hooks existed but were documented nowhere together: ~/.localenv and ~/.localprofile were mentioned in passing, the skip file under the link system, and the ssh, git, Hammerspoon, Ghostty and Alacritty ones only in the config files that read them. Anyone -- an agent especially -- asked to change one machine had to read the whole repo to find out whether that was possible without committing to it. They are one table now, with what each overrides and what reads it, plus what has no hook at all. And the rule for everything else: say what is being asked for and where it would have to live, rather than putting one machine's preference in the config every machine shares, or leaving that machine's checkout dirty and its sync failing.
2026-09-21link: a part named in ~/.config/dot/skip does nothing on that machineIgor Soarez
A machine may need one of the parts left out: on a laptop it does not own, ~/.claude/settings.json is the owner's, holding their environment and plugins, and linking this account's over it is wrong in both directions -- theirs is lost, and anything of theirs worth keeping would have to be carried here, in the repo every machine shares. The file is hand-written and in no repo, like ~/.localenv, so the exception stays on the machine that needs it. The check is in link/lib.sh, as each part starts, rather than in link.sh's loop, so `link/claude.sh yes` obeys it too; link.sh and other repos' link.sh source that file as well, and sit outside link/, so their names can never be read as a part's.
2026-09-17dotfilesIgor Soarez
Shell, editor and terminal configuration, the tools that go with them, and szecret, an age-based secret manager whose store lives elsewhere. History restarts here. What came before was not written to be read by anyone else, and carried machine names, addresses and an encrypted secret store; it is kept privately instead. What is left is meant to be safe on any machine, including one whose owner is not me: see CLAUDE.md for the rule it is written to.