Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LSP diagnostic are highlighted, even when disabled #8550

Closed
yo-main opened this issue Oct 16, 2023 · 1 comment · Fixed by #8551
Closed

LSP diagnostic are highlighted, even when disabled #8550

yo-main opened this issue Oct 16, 2023 · 1 comment · Fixed by #8551
Labels
C-bug Category: This is a bug

Comments

@yo-main
Copy link
Contributor

yo-main commented Oct 16, 2023

Summary

I use multiple lsp and I disable diagnostics feature for one of them. It hides the diagnotic message from that lsp as expected, however I still see the highlight in the editor.

Exemple:
image

Reproduction Steps

I guess you could reproduce it with any other language as long as you have are able to show some diagnostic messages and disable the diagnostics feature of your lsp.

I'm using python so I can reproduce that using a properly configured python env.

This is my language.toml configuration:

[language-server.pylsp]
command = "pylsp"

[language-server.pylsp]
command = "pylsp"

[[language]]
name = "python"
language-servers = [{ name = "pylsp", except-features = [ "diagnostics" ]}]

Create a python env and install some dependencies:

mkdir helix_is_awesome
cd helix_is_awesome
python -m venv .venv
source .venv/bin/activate

pip install python-lsp-server
pip install flake8

cat 'print(1)' > test.py
cat import logging >> test.py

hx test.py

When you open ŧest.py, depending on whether or not diagnostics is enabled, you'll see the warning message. But the highlight will never disappear.

Helix log

No response

Platform

Linux

Terminal Emulator

alacritty

Helix Version

d9d7f67

@yo-main yo-main added the C-bug Category: This is a bug label Oct 16, 2023
@yo-main
Copy link
Contributor Author

yo-main commented Oct 16, 2023

I have the following PR as an attempt to fix that issue: #8551

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant