From cc20d0e9d92fdc28d9b02ea9f83f6f08099551c1 Mon Sep 17 00:00:00 2001 From: l0ng-ai <24760907+l0ng-ai@users.noreply.github.com> Date: Fri, 14 Aug 2026 16:05:43 +0800 Subject: [PATCH] docs(shell): name custom arguments as a reason integration never engaged MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A pane that never armed shell integration blamed a PTY wrapper or an unsupported shell setup. Since #629 a zsh or fish the user gave arguments to is deliberately left alone, so the notice now names that first — it is the one cause the user can undo. All three locales. The release notes gained the matching entry: the change turns integration off for an existing config that sets `shell` or a `custom_shells` entry with `args`, which is worth stating outright. --- CHANGELOG.md | 12 ++++++++++++ src/ui/i18n/en.rs | 4 ++-- src/ui/i18n/ja.rs | 3 ++- src/ui/i18n/zh.rs | 3 ++- 4 files changed, 18 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4fef9522..02c2409e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -48,6 +48,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Changed +- **A zsh or fish you gave your own arguments to is no longer injected into.** + Custom arguments have always been the line where tty7 backs off — the bash, + PowerShell and WSL setups checked for them — but the zsh and fish setups did + not, so a `fish` started with your flags had `-C