From 1170e6e9c11b6061b00bcf2a5506f22f28665bd9 Mon Sep 17 00:00:00 2001 From: JakeBreath Date: Fri, 18 Sep 2026 14:11:10 -0500 Subject: [PATCH] Updates --- .gitignore | 1 + extras/fish_greeting/README.md | 20 ++++++++++++++++++++ 2 files changed, 21 insertions(+) diff --git a/.gitignore b/.gitignore index 11b7085..747b0c4 100644 --- a/.gitignore +++ b/.gitignore @@ -25,6 +25,7 @@ frontend/dist/ .vscode/ .idea/ .DS_Store +.directory # Tooling *.log diff --git a/extras/fish_greeting/README.md b/extras/fish_greeting/README.md index b7aac79..98ab75c 100644 --- a/extras/fish_greeting/README.md +++ b/extras/fish_greeting/README.md @@ -34,6 +34,13 @@ the tools it needs and then verifies the backend: `/health` must answer and a random roll is attempted. It exits non-zero when the backend cannot be reached. +It also appends a guarded block to `~/.config/fish/config.fish` that sources +the function. That is needed on setups whose distro/theme config (CachyOS, +Oh My Fish, hand-rolled `config.fish`) defines `fish_greeting` inline while +the shell starts — such a definition wins over autoloading from +`functions/`, so ours has to be loaded afterwards. The block is written once +and repeated installs leave it alone; pass `--no-config` to skip it. + Non-interactive / re-install: ```fish @@ -89,6 +96,19 @@ guest and sees the public library only. ## Troubleshooting +- **The distro/theme greeting still shows** (CachyOS, Oh My Fish, …): those + configs define `fish_greeting` while the shell starts, which beats + autoloading. Check what fish resolved: + `functions --details fish_greeting` — it must point at + `~/.config/fish/functions/fish_greeting.fish`. If it points at a distro + file, run `fish install.fish` again (it adds the source block to + `config.fish`) or add it yourself: + ```fish + if test -f ~/.config/fish/functions/fish_greeting.fish + source ~/.config/fish/functions/fish_greeting.fish + end + ``` + at the **end** of `~/.config/fish/config.fish`. - `No logo (No image matches those filters.)` — the library has no images for that rating; try another mode or add files. - `No logo (API error)` — check `J621_BASE`, and that the deployment is up