mirror of
https://github.com/stablyai/orca.git
synced 2026-11-19 04:23:57 +00:00
* fix(terminal): drop FORCE_HYPERLINK=1 from PTY spawn env FORCE_HYPERLINK=1 was set on every local PTY. It is read by oh-my-zsh's supports_hyperlinks(), the Rust supports-hyperlinks crate, GNU coreutils, and other tooling — so forcing it on makes every subprocess invoked during shell init take extra branches and emit OSC-8 escapes. Reproduced locally with a heavy zshrc (oh-my-zsh + p10k + nvm + pyenv): time-to-prompt jumps from ~600 ms without the variable to ~2000 ms with it (3.2×) on a clean sandbox. Stacked with the user-reported configuration (conda init, gcloud completions, compaudit over Homebrew paths, corporate network calls) that multiplier applied to a long serial chain of forks can stretch into "terminal is effectively never ready." xterm still renders OSC-8 hyperlinks when tools emit them on their own detection, so link support in Orca is preserved. VS Code does not set this variable either. * feat(terminal): make FORCE_HYPERLINK opt-out via settings, default on The previous commit on this branch removed FORCE_HYPERLINK=1 from PTY spawn env entirely. Revise: keep the historical default (on) so existing users don't silently lose OSC-8 hyperlink emission from tooling that checks this flag, but expose a toggle in Settings → Terminal → Advanced so users with heavy rc files (oh-my-zsh + powerlevel10k + nvm + pyenv + conda, etc.) can turn it off and reclaim the shell-startup time that the extra subprocess branching and escape emission was costing them. - Add `terminalForceHyperlink: boolean` to GlobalSettings (default true) - LocalPtyProvider gains an `isForceHyperlinkEnabled` hook; IPC wires it from the live settings snapshot - New SearchableSetting row in TerminalPane with zshrc-adjacent search keywords so users troubleshooting slow startup find it - Unit tests cover both default-on and opt-out paths