From 7610a4121d47bafd32cb72e5195925d44888bf80 Mon Sep 17 00:00:00 2001 From: rootiest Date: Wed, 3 Jun 2026 21:11:34 -0400 Subject: [PATCH] docs(readme): simplify return sentinel callout wording --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6ada37b..25fb07e 100644 --- a/README.md +++ b/README.md @@ -676,7 +676,7 @@ Then open a new Fish shell — Fisher and all plugins will be installed automati A [chezmoi](https://www.chezmoi.io/) dotfile manager is also configured — secrets are sourced from `~/.config/.user-dots/fish/secrets.fish` and excluded from version control. > [!IMPORTANT] -> `config.fish` contains two `return` sentinel guards. One sits at the end of the `if status is-interactive` block and one sits at the very end of the file. Together they prevent any lines appended **after** either point from executing. Many tools (starship, zoxide, mise, etc.) offer a setup command that appends an `init | source` line to your `config.fish` — those lines will silently have no effect here. All integrations are managed through `conf.d/` files instead. If you add a new tool and its shell integration appears to do nothing, check whether it appended an init line to the bottom of `config.fish` and create a `conf.d/.fish` file for it instead. +> `config.fish` ends with a `return` sentinel guard. Any lines appended **after** it by a tool's setup command will silently have no effect. Many tools (starship, zoxide, mise, etc.) offer a setup command that appends an `init | source` line to your `config.fish` — all integrations are managed through `conf.d/` files instead. If you add a new tool and its shell integration appears to do nothing, check whether its setup command appended an init line to the bottom of `config.fish` and create a `conf.d/.fish` file for it instead. --- ## Personalization