Clojurians Log v2

OK https://github.com/BetterThanTomorrow/calva/issues/1023. I'm fairly clueless about how to proceed, but I'll make a bit of time late in the week to investigate.

Attaching the gif here since the shared post doesn’t include it. 😃

It is pretty amazing how fast kondo is to report on the issues with reordering the bindings.

How do you make these gifs?

I want to make one with my backspace positional thing. That may warm some hearts.

I use GIF Brewery. It’s free as in beer. Crashes on me some times, but otherwise is very nice and produces crisp gifs. You can crop it both in time and space. Don’t know if it is available for Linux though

I use Peek on linux - if that's what you use

Welcome @jonoflayham!

Thanks! Here because I’m considering leaving IntelliJ…

I am enjoying my time with Calva and am astonished by the pace of the Calva team. I think you are at least 8 borks on the borkdude productivity meter!

Haha, I think we might be an 8th bork, but that is pretty impressive! 😃

Super happy for your kind words, @lee. Thanks! ❤️

Hey, personally I rate 0.1 productivity borks on a good day. :simple_smile: I’m happy with it, but am always impressed when I see productive teams!

VS Code already updated Calva and I just tried out that new dragging feature: very nice! I don't know if I'll ever be able to remember the key chord for it, mind you 🙂 (but I have the command palette)

Try to remember the shortcuts for dragging forms out of and into lists backward and forward, and then maybe these in-list ones will seem easy. 😃

As a Calva noob, I am wondering if Calva/lsp looks at my local project clj-kondo hooks. I ask because I am getting warnings in Calva for things my hooks do handle when running clj-kondo from the command line.

Hm, can you provide a repro case in an issue?

We are all a bit of Calva+lsp noobs, @lee. However, @brandon.ringe and @ericdallo are an amazing team to watch when they are trying to tame this beast.

@lee, clojure-lsp should use your .clj-kondo/config.edn just like if you were using only clj-kondo

Ok, cool. I’m happy to provide a repro in an issue. I’ll start with just linking to my project and describing, and then can isolate more at your request.

Raise in calva or clojure-lsp?

I'd sugges open the issue on Calva, then we could analyze and open on clojure-lsp if it's a bug there 😉

Backspace positional in calva-extras - powerlevel 80%. (For the rest 20% I need sexp parsing apis.)

Thanks team Calva, https://github.com/BetterThanTomorrow/calva/issues/1026, ignore my mention of clj-kondo hooks here on Slack, think I was on the wrong track there!

You can temporarily disable diagnostics in LSP and use the standalone clj-kondo VSCode plugin

Ah, did not know I could do that, thanks! Will do and update issue.

This is what I do in emacs as well, since I usually run a bleeding edge clj-kondo

How do I disable diagnostics in LSP?

I don't know about Calva but in emacs I set the variable lsp-diagnostics-provider :none

Probably Calva does not support that 😕 but I'd not recommend doing this since the lint on the file reflects on clj-kondo analysis, so your code could show it's correct because of a newer version of clj-kondo or something like that, but clojure-lsp is not being able to parse the code or understands it

Of course the underlying problem should be addressed, this is why I said 'temporarily' :)

But even if you turn off diagnostics, clojure-lsp should be able to invoke clj-kondo for analysis

yes, a temporary flag on Calva could help on thses cases 😉

Ok, I shall leave issue as-is then.

I double checked and I don't think it's an issue with clj-kondo itself, rather an issue with maybe not picking up the config correctly in lsp / calva (not sure how these are wired up together)

Maybe it would help if calva / lsp could display the effective config used somehow

You can see this when invoking clj-kondo.core/run! and then pprinting the returned :config

Related issue here @lee: https://github.com/BetterThanTomorrow/calva/issues/980

More discussion in the linked PR

Yeah, confirmed the issue is on clojure-lsp side, it's using the home clj-kondo dir instead of the project config 😕

Hey, that was quick, and probably an easy fix! Nice!

🤞 Looking into it right now

Created this issue to track it: https://github.com/clojure-lsp/clojure-lsp/issues/308

@borkdude I wondering if clojure-lsp should find the clj-kondo config to pass it via the clj-kondo API

clj-kondo already has logic to find its config. why pass it?

Is there any way to pass some configs that we want (like cache, analysis etc) but still make clj-kondo keep the behaviour of find the configs

yes, you just pass :config which is a vector of additional configs which will be merged into the config that the user already has in .clj-kondo

oh perfect, I think the issue is that ATM clojure-lsp is merging with a config from .lsp/config.edn (probably leftover after kondo integration 😅)

will do the test right now

💤 👋