zed/crates/cli
Lukas Wirth 2471ae451c
Pre-initialize global rayon threadpool (#41226)
We only use it a handful of times and the default amount of threads
(logical cpu core number) its spawns is overkill for this. This also
gives the threads names oppose to being labeled `<unknown>`

Release Notes:

- N/A *or* Added/Fixed/Improved ...
2025-10-26 12:44:34 +00:00
..
src Pre-initialize global rayon threadpool (#41226) 2025-10-26 12:44:34 +00:00
build.rs Forbid std::process::Command spawning, replace with smol where appropriate (#38894) 2025-09-26 15:17:36 +00:00
Cargo.toml Pre-initialize global rayon threadpool (#41226) 2025-10-26 12:44:34 +00:00
LICENSE-GPL chore: Change AGPL-licensed crates to GPL (except for collab) (#4231) 2024-01-24 00:26:58 +01:00
README.md remote: Support line and column numbers for remote paths (#40410) 2025-10-17 10:50:22 +00:00

Cli

Testing

You can test your changes to the cli crate by first building the main zed binary:

cargo build -p zed

And then building and running the cli crate with the following parameters:

 cargo run -p cli -- --zed ./target/debug/zed.exe