Summary
If I open zed in a directory, e.g., "zed ~/Desktop", then terminal panels open in that directory, as per the settings.
If I open an individual file in the directory, e.g., "zed hello.txt", then terminal panels open in the root directory /, which is (a) useless and (b) inconsistent with the behavior above.
I think a more sensible behavior would be that, when zed is used to open an individual file, it should consider that file's path as "the project directory", and open terminal panels there.
Description
Steps to reproduce (verified on MacOS, arm64, Zed 0.212.6):
- create a file, e.g.,
echo hello > ~/Desktop/hello.txt
- open that file in zed
zed ~/Desktop/hello.txt
- open a terminal panel in zed
Expected Behavior:
The terminal opens in ~/Desktop
Actual Behavior:
The terminal opens in /
Zed Version and System Specs
Zed: v0.212.6 (Zed)
OS: macOS 26.1
Memory: 16 GiB
Architecture: aarch64
If applicable, attach your Zed.log file to this issue.
Zed.log
Summary
If I open zed in a directory, e.g., "zed ~/Desktop", then terminal panels open in that directory, as per the settings.
If I open an individual file in the directory, e.g., "zed hello.txt", then terminal panels open in the root directory /, which is (a) useless and (b) inconsistent with the behavior above.
I think a more sensible behavior would be that, when zed is used to open an individual file, it should consider that file's path as "the project directory", and open terminal panels there.
Description
Steps to reproduce (verified on MacOS, arm64, Zed 0.212.6):
echo hello > ~/Desktop/hello.txtzed ~/Desktop/hello.txtExpected Behavior:
The terminal opens in ~/Desktop
Actual Behavior:
The terminal opens in /
Zed Version and System Specs
Zed: v0.212.6 (Zed)
OS: macOS 26.1
Memory: 16 GiB
Architecture: aarch64
If applicable, attach your
Zed.logfile to this issue.Zed.log