Fork me on GitHub
#lsp
<
2023-01-06
>
Derek01:01:55

Seeing some flycheck ‘issues’ coming back with level lsp-fly... instead of warning. When I run clj-kondo manually, they are reported as warning. Details in thread

Derek01:01:20

$ clojure-lsp --version
clojure-lsp 2022.12.09-15.51.10
clj-kondo 2022.12.08

Derek01:01:21

flycheck                       20221213.107
lsp-mode                       20221231.746

Derek01:01:37

GNU Emacs 28.2 (build 1, x86_64-apple-darwin21.6.0, Carbon Version 165 AppKit 2113.6) of 2022-09-14

Derek01:01:32

$ clj-kondo --lint src/org/passen/malapropism/core.clj 
src/org/passen/malapropism/core.clj:13:13: warning: Unused import PushbackReader
linting took 24ms, errors: 0, warnings: 1

Derek01:01:23

$ clojure-lsp diagnostics
[100%] Project analyzed
Finding diagnostics...
src/org/passen/malapropism/core.clj:12:12: warning: [unused-import] Unused import PushbackReader

ericdallo10:01:15

That's odd, looks like a emacs issue, maybe some bad compilation package or outdated package

Derek15:01:15

Deleted everything in ~/.emacs.d/elpa — no change

Derek15:01:58

It’s not every warning/error that comes through that way

ericdallo15:01:43

hum, maybe it's some missing face

ericdallo15:01:58

would be nice to understand if we could know the complete name of that lsp-fly...

Derek15:01:12

Agree. Any idea how to expand that column? Or see the raw data?

Derek15:01:06

lsp-flycheck-warning-unnecessary

ericdallo15:01:13

maybe changing flycheck-error-list-format variable?

ericdallo15:01:27

hum, indeed I get the same on my emacs, but not sure it's a problem

Derek15:01:30

I wouldn’t say it’s a problem, but there are packages that rely on more standard Levels

ericdallo15:01:28

I see, also I don't see a problem marking it on flycheck as warn, but we would need to discuss with more lsp-mode people, so please open a issue there, not sure too if it's possible to change what is presented on flycjec error buffer without affecting anything more

Derek15:01:13

Ok — will do