fix(railguard): install from fork + land stranded setup-unification follow-ups - #44
Merged
Merged
Conversation
marzocchi/zsh-notify only supports iTerm/Apple Terminal (macOS) and X11 (Linux), so it printed "unsupported environment" and disabled itself on the whole Ghostty + Wayland fleet — it never sent a single notification on any machine. Replace it with a precmd/preexec hook in the deployed zshrc that calls terminal-notifier (macOS) / notify-send (Linux) directly, no focus detection. Drop the plugin and the now-unused xdotool package. - Prepend _notify_precmd to precmd_functions so it reads the real command $? before p10k's hook (loaded via antidote) resets it; otherwise every long command was labelled "finished". - Escape Pango markup metachars in the notify-send body so commands containing &, <, > render intact. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- verify: check Ghostty config at `config` (not `config.ghostty`) so a healthy macOS install no longer reports MISSING - p10k: move p10k.zsh.example to dotfiles/ and deploy it on macOS too, so fresh Macs don't drop into the p10k configure wizard - set -e safety: tolerate antidote pre-clone failure (server), getent failure (set_default_shell), and codeburn menubar failure (macOS) instead of aborting the whole run - args: reject missing/flag-shaped --platform|--distro value in both core and verify parsers (was silent abort / flag-swallowing) - reminders: surface priority:"none" custom and app-store entries, per the documented "reminders only" contract (llama.cpp, Pixelmator, etc.) - zshrc: gate notify-send on WAYLAND_DISPLAY/DISPLAY (no D-Bus spam over SSH) and make _notify_start read nounset-safe - pyenv: use grep -qF for the installed-version check to avoid regex dot-wildcard false matches Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Point `cargo install` at https://github.com/ulises-c/railguard and drop the binary-exists guard so existing crates.io installs get switched over to the fork on re-run, while staying a no-op when already up to date. Falls back gracefully when cargo is absent but a binary already exists. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lands three commits that were stranded on
feat/setup-unificationafter PR #37 merged (the branch was reused and pushed post-merge, never re-PR'd), rebased cleanly onto currentmain.cargo installathttps://github.com/ulises-c/railguardand drop the binary-exists guard so existing crates.io installs switch over to the fork on re-run, staying a no-op when already up to date. Falls back gracefully when cargo is absent but a binary already exists.Notes
Opened as a new branch (
feat/setup-unification-followups) rather than reusingfeat/setup-unification, since PR #37 is already merged/closed and the old branch diverged frommain.🤖 Generated with Claude Code