Inline diagnostics rendering error

[godalming123]

Summary

I've found a case where the rendering of the inline diagnostics makes it impossible to see which error is associated with which part of a line.

Reproduction Steps

I tried this:

1. hx
2. Find a way to create multiple LSP errors on one line
3. Zoom in until it is not possible to know which error comes from which part of the line

I expected this to happen:

The lines that connect the error to the part of the code that caused it do not overlap unless multiple errors were caused by the same part of code.

Instead, this happened:

Helix log

~/.cache/helix/helix.log

The log file was too big for github to let me include it as text.
helix.log

Platform

Linux

Terminal Emulator

Ghostty

Installation Method

Source

Helix Version

helix 25.01.1 (523e8aa)

[pascalkuthe]

This is intentional in cases where the diagnostics is so far to the right that there would be not enligh space to show the text

[godalming123]

But there is enough space in this case.

The current rendering:

How I would render it:

                                                                      b a
│                                        ┌────────────────────────────┘ │
│                                        │┌─────────────────────────────┘
│                                        │├─ Expression value is unused
│                                        │├─ "a" is not defined
│                                        │└─ Statements must be separated
│                                        │   by newlines or semicolons
│                                        ├─ Expression value is unused
│                                        └─ "b" is not defined
└─ Unexpected indentation