Anthony Eid e5b98a5f19 Accept shell environment after non-zero shell exit (#55175) ... Summary: When a user shell hook returned an error, Zed would fail to load the shell environment even if the captured environment output was still valid. This could prevent the terminal panel and other shell-dependent features, such as the debugger and agent panel, from creating terminals or running commands. That is especially disruptive when the shell environment is valid and a terminal could otherwise still be used. Zed now ignores the non-zero shell exit in this case when it can still parse a valid shell environment, allowing those features to continue working. Self-Review Checklist: - [x] I have reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Release Notes: - Fixed shell environment loading when login shells exit non-zero after printing environment variables.		2026-04-29 11:56:56 +00:00
..
src	Accept shell environment after non-zero shell exit (#55175)	2026-04-29 11:56:56 +00:00
Cargo.toml	Remove std::fs::read_link in fs (#50974)	2026-03-14 20:02:34 -04:00
LICENSE-APACHE