You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, helix is awesome! So glad to have this project. Keep up the excellent work, everyone!
I'm on a small laptop with vertical window splits, so I don't have very many columns. tput cols shows 194, so one vertical split cuts that in half, then there's a | column showing the separator, then each buffer has something like 6-10 columns for error indicators, line numbers, etc… so I estimate maybe 87 columns per buffer.
Here's what the display looks like in my editor right now:
The error message obscures my code, including the current cursor/selection.
Reproduction Steps
I tried this:
hx
Split the window vertically: C-W v
Edit some code to introduce an LSP error.
I expected this to happen:
I'm not sure! Obscuring either the code or the error message is confusing/annoying.
The UI I personally would prefer is for all LSP errors to appear in a separate window at the bottom of the terminal, completely out of band for the code. The location of the error would be implicit in the selection/cursor, or perhaps the left line-based error indicator would have a special color/glyph to indicate which line this new LSP message widget applies to.
Another UI option might be to have a key combo to toggle between displaying or hiding the LSP error.
My personal preference would be for a combination of these: a dedicated widget at the bottom of the terminal that I can quickly pop open or hide, depending on my needs in the moment.
(And yes, perhaps a nicer UI is just a bigger screen, but I'm on this small form factor laptop because it's so convenient to take with me on trips.)
Instead, this happened:
The LSP messages are displayed right-justified within the same buffer view as source, so it ends up obscuring the source.
Helix log
This doesn't seem relevant. All of the behavior is as-designed AFAIK. LMK if log messages are important here.
Summary
First off, helix is awesome! So glad to have this project. Keep up the excellent work, everyone!
I'm on a small laptop with vertical window splits, so I don't have very many columns.
tput cols
shows 194, so one vertical split cuts that in half, then there's a|
column showing the separator, then each buffer has something like 6-10 columns for error indicators, line numbers, etc… so I estimate maybe 87 columns per buffer.Here's what the display looks like in my editor right now:
The error message obscures my code, including the current cursor/selection.
Reproduction Steps
I tried this:
hx
C-W v
I expected this to happen:
I'm not sure! Obscuring either the code or the error message is confusing/annoying.
The UI I personally would prefer is for all LSP errors to appear in a separate window at the bottom of the terminal, completely out of band for the code. The location of the error would be implicit in the selection/cursor, or perhaps the left line-based error indicator would have a special color/glyph to indicate which line this new LSP message widget applies to.
Another UI option might be to have a key combo to toggle between displaying or hiding the LSP error.
My personal preference would be for a combination of these: a dedicated widget at the bottom of the terminal that I can quickly pop open or hide, depending on my needs in the moment.
(And yes, perhaps a nicer UI is just a bigger screen, but I'm on this small form factor laptop because it's so convenient to take with me on trips.)
Instead, this happened:
The LSP messages are displayed right-justified within the same buffer view as source, so it ends up obscuring the source.
Helix log
This doesn't seem relevant. All of the behavior is as-designed AFAIK. LMK if log messages are important here.
Platform
linux (crostini within ChromeOS)
Terminal Emulator
hx inside tmux inside ChromeOS Termina
Helix Version
helix 23.03 (92c328c)
The text was updated successfully, but these errors were encountered: