Thorsten Ball b05aa381aa Handle old versions of /usr/bin/env when loading shell env (#10202) ... This fixes #9786 by using an invocation of `/usr/bin/env` that's supported by macOS 12. As it turns out, on macOS 12 (and maybe 13?) `/usr/bin/env` doesn't support the `-0` flag. In our case it would silently fail, since we `exit 0` in our shell invocation and because the program we run and whose exit code we check is the `$SHELL` and not `/usr/bin/env`. What this change does is to drop the `-0` and instead split the environment on `\n`. This works even if an environment variable contains a newline character because that would then be escaped. Release Notes: - Fixed Zed not picking up shell environments correctly when running on macOS 12. ([#9786](https://github.com/zed-industries/zed/issues/9786)). Co-authored-by: Dave Smith <davesmithsemail@gmail.com>		2024-04-05 15:46:56 +02:00
..
src	Handle old versions of /usr/bin/env when loading shell env (#10202)	2024-04-05 15:46:56 +02:00
Cargo.toml	Add git blame (#8889)	2024-03-28 18:32:11 +01:00
LICENSE-GPL	chore: Change AGPL-licensed crates to GPL (except for collab) (#4231)	2024-01-24 00:26:58 +01:00