Skip to content

Log syntax highlighting does not differentiate INFO and WARNING levels without brackets #19

@fakhrulnurmulyana

Description

@fakhrulnurmulyana

Hi, thank you for the great work on the Zed log syntax highlighting 🙌

I noticed a limitation when working with log formats that do not use square brackets for log levels.

Current Behavior

In my log format, entries look like this:

2026-03-31 20:10:46,166 | INFO | job_tracker.infrastructure.scraper | Fetch Success
2026-03-31 20:16:59,274 | WARNING | google_genai.types | Warning: there are non-text parts...

Currently, both INFO and WARNING appear with the same color, making it harder to visually distinguish log severity levels.

Expected Behavior

It would be very helpful if different log levels (INFO, WARNING, ERROR, etc.) had distinct colors even without requiring square bracket formatting, like:

[INFO]
[WARNING]

Reference

In the documentation/examples, highlighting works when levels are wrapped in brackets:

[INFO], [WARN], [ERROR]

Suggestion

It might be useful to:

  • Support common log patterns like | INFO |, | WARNING |, etc.
  • Or allow configurable patterns for log level detection

Additional Context

This is how it appears in VS Code (which already distinguishes levels correctly):

  • INFO → different color
  • WARNING → different color

It would be great if Zed could support similar flexibility.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions