> Unused private var config-compilation.yaml/whitespace-names [141, 2]

Should the colum here be 16, rather than 2?

(def ^:private whitespace-names
 ^2            ^16

it's kind of arbitrary I'd say

if you're trying to exclude warnings based on position, maybe only use the line number?

there has been a recent change to that position for ... reasons 🙂

if there is a strong case to change it, I'd like to hear it

I tried to make it consistent with joker so if you use both, you see it only in place:

$ clj-kondo --lint /tmp/foo.clj
/tmp/foo.clj:3:1: warning: Unused private var private.tmp.foo/foo
linting took 9ms, errors: 0, warnings: 1

$ joker --lint /tmp/foo.clj
/tmp/foo.clj:3:1: Parse warning: unused var foo (joker)

I do not have a strong case.

When the squiggle in VSCode is under the def, it makes me think that there is problem with the def form.

If the squiggle were under the var name, I would assume the problem was with the var itself.

ok, that sounds like a case

the way it works now is that the var is defined at that position, so in the export you will also have that position

and because the var is defined at that position, the warning also appears there

but that could be easily changed probably (while keeping the export the same)

I don't have a strong preference

please give it a try: https://marketplace.visualstudio.com/items?itemName=borkdude.clj-kondo this should work for users on Windows as well

messages about unresolved symbols and such show up 🙂

though i wonder why i get one for "alias"