zed icon indicating copy to clipboard operation
zed copied to clipboard

extension_builder does not use project environment PATH?

Open abustany opened this issue 1 month ago • 0 comments

Summary

Building a dev extension is not possible if rustc is not in the system PATH

Description

I'm on a system where rustc is not directly in the PATH, but requires some environment setup. In a shell that's correctly setup (rustc --version works) I start zed (using zed .) and choose the "Install dev extension" action, but the build fails because rustc is not found.

In my case I'm using a nix flake to manage the rust version, but any setup where the PATH first needs to be set for rustc to become available would be the same I suppose.

Steps to reproduce:

  1. Have a Rust install in a path outside the system PATH
  2. Start a shell where rustc is available (PATH set to correct value)
  3. Start zed from that shell
  4. Use the "Install dev extension" action

Expected Behavior: Build fails because rustc is not found

Actual Behavior: zed uses the parent shell environment and builds the extension using the correct rustc version

Zed Version and System Specs

Zed: v0.213.4 (Zed) OS: macOS 26.1 Memory: 48 GiB Architecture: aarch64

If applicable, attach your Zed.log file to this issue.

No response

abustany avatar Nov 23 '25 22:11 abustany