Zed

./script/linux
./script/install-mold 2.34.0
echo "nightly" > crates/zed/RELEASE_CHANNEL
./script/bundle-linux

git config --system core.longpaths true

sudo apt-get update
sudo apt-get install -y wget software-properties-common

sudo apt-get update
sudo apt-get install -y mingw-w64 powershell

sudo apt-get update
sudo apt-get install -y mingw-w64

rustup target add x86_64-pc-windows-gnu

cargo build --target x86_64-pc-windows-gnu --release --package zed --package cli

pwsh script/bundle-windows.ps1

export CC_x86_64_pc_windows_gnu=x86_64-w64-mingw32-gcc
export CXX_x86_64_pc_windows_gnu=x86_64-w64-mingw32-g++

echo 'export CC_x86_64_pc_windows_gnu=x86_64-w64-mingw32-gcc' >> ~/.bashrc
echo 'export CXX_x86_64_pc_windows_gnu=x86_64-w64-mingw32-g++' >> ~/.bashrc
source ~/.bashrc

echo "nightly" > crates/zed/RELEASE_CHANNEL

cargo install cargo-about

cargo build --target x86_64-pc-windows-gnu --release --package zed --package cli

sudo apt-get update
sudo apt-get install -y spirv-tools

wget https://github.com/microsoft/DirectXShaderCompiler/releases/download/v1.7.2212/dxc_2022_12_08.zip
unzip dxc_2022_12_08.zip -d dxc
export PATH=$PATH:/workspace/code/dxc/bin

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.

Installation

On macOS and Linux you can download Zed directly or install Zed via your local package manager.

Other platforms are not yet available:

Windows (tracking issue)
Web (tracking issue)

Developing Zed

Building Zed for macOS
Building Zed for Linux
Building Zed for Windows
Running Collaboration Locally

Contributing

See CONTRIBUTING.md for ways you can contribute to Zed.

Also... we're hiring! Check out our jobs page for open roles.

Licensing

License information for third party dependencies must be correctly provided for CI to pass.

We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:

Is it showing a no license specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
Is the error failed to satisfy license requirements for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the accepted array in script/licenses/zed-licenses.toml.
Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!