mixa/zed

Files

Lukas Wirth 9af6e82e65 language: Only block the foreground on buffer reparsing when necessary (#43888 )

Gist is we only need to block the foreground thread for reparsing if
immediate language changes are useful to the user. That is usually only
the case when they edit the buffer

Release Notes:

- Improved performance of large project searches and project diffs

Co-authored by: David Kleingeld <david@zed.dev>

2025-12-01 14:57:15 +01:00

src

language: Only block the foreground on buffer reparsing when necessary (#43888 )

2025-12-01 14:57:15 +01:00

Cargo.toml

Remove workspace-hack (#40216 )

2025-10-17 18:58:14 +00:00

LICENSE-GPL

zlog: Init (#27273 )

2025-03-21 20:08:03 +00:00

README.md

cli: Allow opening non-existent paths (#43250 )

2025-11-24 11:30:19 +02:00

README.md

Zlog

Use the ZED_LOG environment variable to control logging output for Zed applications and libraries. The variable accepts a comma-separated list of directives that specify logging levels for different modules (crates). The general format is for instance:

ZED_LOG=info,project=debug,agent=off

Levels can be one of: off/none, error, warn, info, debug, or trace.
You don't need to specify the global level, default is trace in the crate and info set by RUST_LOG in Zed.