From 352bd588135b62f0da548d22188c829143bdbe32 Mon Sep 17 00:00:00 2001 From: Igor Soarez Date: Mon, 21 Sep 2026 14:37:35 +0300 Subject: install.sh: install Homebrew, add bash, and seed the colour files Three things a machine set up from this repo alone hit on its first run: Homebrew was a dead end -- install.sh printed the command and exited, leaving the one prerequisite everything else needs to be run by hand. It installs it now, NONINTERACTIVE so it does not wait on a RETURN; the sudo password is still asked for, which is why this script is run by hand. bash was missing from the Brewfile, so bin/open and secrets/ ran under the 3.2 macOS ships and failed on `${v,,}`; config/bashrc also looks for the bash-completion 2.x that wants 4.2. Ghostty refused to start -- "error opening config-file ... error.FileNotFound" -- because config-file pointed at the colour file bin/theme writes, which does not exist until theme has run. The include is optional now (`?`), and this script seeds the colour files when a machine has none, leaving a machine that already has a theme alone. --- config/ghostty/config | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'config') diff --git a/config/ghostty/config b/config/ghostty/config index 67393b4..0cb6f65 100644 --- a/config/ghostty/config +++ b/config/ghostty/config @@ -30,8 +30,11 @@ font-size = 12 # theme = Monokai Soda # theme = Builtin Light -# Import color scheme (managed by theme script) -config-file = ~/.local/share/ghostty/color +# Import color scheme (managed by theme script). The leading `?` makes it +# optional: bin/theme writes that file, so until it has run on this machine the +# file does not exist, and a plain config-file makes Ghostty refuse to start +# with "error opening config-file ... error.FileNotFound". +config-file = ?~/.local/share/ghostty/color # Shader # custom-shader = ~/.config/ghostty/shader.glsl -- cgit v1.2.3