Files
zed/crates/zlog
Leonard SeiboldandJohn Tur 1f2a319d40 gpui: Remove blade, reimplement linux renderer with wgpu (#46758)
The blade graphics library is a mess and causes several issues for both
Zed users as well as other 3rd party apps using GPUI. This PR removes
blade and implements the linux platform using `wgpu` which is the
de-facto standard in the rust UI and graphics ecosystem. This will not
just fix [issues that Zed users have
today](https://github.com/YaLTeR/niri/issues/2335), but also profit from
wgpu improvements in the futures, from other projects contributing (such
as the bevy game engine, Iced, or pretty much every other relevant
project).

This will close several related issues on the zed repo as well. See
https://github.com/zed-industries/zed/issues?q=frozen%20nvidia%20linux
(probably not all of them, have only tested the freeze on nvidia and
Smithay-based wayland compositors).

Some related issues:
https://github.com/zed-industries/zed/issues/44814
https://github.com/zed-industries/zed/issues/40481
https://github.com/YaLTeR/niri/issues/2335
https://github.com/zortax/zlaunch/issues/15

Would appreciate feedback if this is something the zed maintainers would
be interested in.

Release Notes:

- N/A

---------

Co-authored-by: John Tur <john-tur@outlook.com>
2026-02-13 02:55:42 -05:00
..
2025-10-17 18:58:14 +00:00
2025-03-21 20:08:03 +00:00

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.