dotfiles/dot_config/zsh/dot_zshrc, branch masterMy linux config and rc fileshttps://git.sommerfeld.dev/dotfiles/atom/dot_config/zsh/dot_zshrc?h=master2026-08-14T13:21:05ZRemove former work environment configuration2026-08-14T13:21:05Zsommerfeldsommerfeld@sommerfeld.dev2026-08-14T13:21:05Zurn:sha1:315e7580b35f2535319bbd852d443c3c9bcb4d41Prune stale dotfiles commentary2026-07-02T10:35:35Zsommerfeldsommerfeld@sommerfeld.dev2026-07-02T10:35:35Zurn:sha1:f0c626059451e1f8621600e610240739d5633560Use local gpg-agent on VM2026-06-19T15:36:01Zsommerfeldsommerfeld@sommerfeld.dev2026-06-19T15:36:01Zurn:sha1:7eacd3c160f23fbff65c510aae70266b33b48bc2Reduce Arch package surface2026-06-18T11:06:20Zsommerfeldsommerfeld@sommerfeld.dev2026-06-18T11:06:20Zurn:sha1:511793cba498f52b0f92904965ea5c9afa8b6ea4Allow unmatched globs in zsh2026-06-17T14:47:38Zsommerfeldsommerfeld@sommerfeld.dev2026-06-17T14:47:38Zurn:sha1:08a1557a6896fe5772374a588cefafcc7e352493Add mosh work VM alias2026-06-14T23:55:43Zsommerfeldsommerfeld@sommerfeld.dev2026-06-14T23:55:43Zurn:sha1:14f5a45a67b2d719e8912c335be8f521e39291fdLimit git switch completion to local branches2026-06-05T10:06:04Zsommerfeldsommerfeld@sommerfeld.dev2026-06-05T10:06:04Zurn:sha1:929f8bea128361822b054db36402b5e19234319ffix(ssh): make agent.sock symlink concurrent-connection-safe2026-05-22T09:41:24Zsommerfeldsommerfeld@sommerfeld.dev2026-05-22T09:41:24Zurn:sha1:982d180f9b9a2f8a90d454816474dce8d4b4b8e2
Previously every new login retargeted ~/.ssh/agent.sock to its own
per-connection forwarded socket. That broke a multi-connection setup
when the most-recent connection (which 'won' the symlink) dropped:
all surviving connections' panes would point at a dead socket until a
fresh login from a surviving connection re-ran zprofile.
zprofile: only retarget when the existing symlink target is dead
(sshd unlinks the per-connection socket on disconnect, so [[ -S ]] on
the resolved path is a reliable liveness probe). First connection
seeds the symlink, subsequent logins keep using it.
ssh-agent-refresh: scan /tmp/ssh-*/agent.* for any live forwarded
socket and retarget to the first that responds to ssh-add. Lets the
surviving connection recover without waiting for a new login shell.
feat(zsh): recover Arch site-functions + HELPDIR after removing system zsh2026-05-22T09:41:24Zsommerfeldsommerfeld@sommerfeld.dev2026-05-22T09:41:24Zurn:sha1:6b7e057bd4fc2cbdffe5fc8b3095810db1ccf9e3
Switching to nix's zsh on the Arch host left two functional gaps the
Arch zsh package used to fill:
1. /usr/share/zsh/site-functions in fpath: pacman, paru, systemctl,
journalctl, flatpak, docker, kubectl, makepkg etc. drop their
completions there. nix zsh's compiled-in fpath doesn't include
/usr/share so we lose all of them silently. Added that path (and
vendor-completions for the VM's apt-installed completions) to the
existing fpath loop, guarded by [[ -d ]].
2. HELPDIR for the run-help / help-alias machinery: needed so 'help cd'
etc. find the per-builtin help docs. Pick the first existing version
dir, preferring nix-profile so it matches the running zsh version.
fix(ssh): stabilise forwarded ssh-agent socket across reconnects2026-05-22T09:41:23Zsommerfeldsommerfeld@sommerfeld.dev2026-05-22T09:41:23Zurn:sha1:159d69ddd122cfdb55d087d754d7472d42fa73ae
Forwarded SSH_AUTH_SOCK lives at /tmp/ssh-XXX/agent.NNN — a
per-connection path that disappears on disconnect, leaving every
long-running zellij pane (and its children: claude-code, nvim, …)
pointing at a dead socket. Reattaching after reconnect doesn't help:
the env was captured when zellij first started.
Fix: maintain ~/.ssh/agent.sock as a symlink, re-aimed at the live
forwarded socket on every login (zprofile). Export the stable path so
processes inherit a value that survives reconnects — git fetch /
commit signing keep working in re-attached zellij panes with zero
per-pane re-export.
Adds 'ssh-agent-refresh' helper for transitional panes still holding
the dead per-connection path: re-exports SSH_AUTH_SOCK to the stable
symlink and validates with ssh-add -l. Already-running children
(claude-code) must still be restarted since env is inherited, not
observed.