Clojurians Log v2
cursive
it helps in so far that if you integrate clj-kondo linting inside Cursive then people would see the correct warnings
but I can imagine this would be a big step and doesn't integrate with the way IntelliJ works
What issue are you having? You need to have ports open, but what I've found useful to do is just use repl within wsl, so for example lein repl then connect to the nrepl port from cursive using the remote repl option 😃...
thanks!!
1
Hey, I was wondering whether there were some renderers that came with Cursive. For instance, when I am debugging, vectors look like in the first picture. I noticed one could add custom renderers like in the second picture. Thanks!
3🤯
Yes, Cursive does use some renderers internally, and it could probably do with more. If there are types that you’d like to see presented differently, I’m interested to know about them. I’d have to check the vector case though, I usually see them presented as lists.
To be honest nice ways of showing more complex stuff in ways that can be expanded, using nav and datify would be cool. I've never really used REBL that much, but if it was to a degree available in cursive that would be amazing...
I’m actually planning that soon, with inline rendering.
1
> How would you like this to work? It's a good question. I'm not very familiar with with konfigs - I am assuming there is enough information to determine the "source" of a symbol/keyword and, thus, that would be enough information to wire up Intellij's Find Usages feature.
> but I can imagine this would be a big step and doesn't integrate with the way IntelliJ works Thanks. I guess it was more wishful thinking than anything else 🙂
I still don’t quite understand. As I understand it, the clj-kondo integration should show the warnings in the editor already, right? And when there’s a warning in the editor, you should be able to use the normal Cursive find usages feature at that point?
> As I understand it, the clj-kondo integration should show the warnings in the editor already, right? This is correct. The other point seems logical too.
But Cursive also emits syntax warnings on its own.
And these are not informed by any clj-kondo configuration
And that was what the question was about: could clj-kondo configuration inform Cursive's own understanding of the syntax, somehow
So is the proposal to control the IntelliJ inspections via the clj-kondo config, i.e. enable and disable the roughly equivalent inspections based on the config? Or to somehow use the clj-kondo analysis results?
I don't think anyone has made a proposal, Mark was just asking about thoughts. I don't have any thoughts on this, but I would be open to help you out with something, if you needed it from the clj-kondo side.
Ok, I’ll wait and see what Mark suggests. I’d be interested to know what the issue around attribute keywords is, for example.
Well, the config for pathom3 is pretty basic: https://github.com/wilkerlucio/pathom3/blob/master/resources/clj-kondo.exports/com.wsscode/pathom3/config.edn I think the same can be accomplished in Cursive with "resolve macro as" if I remember correctly.
Ah, ok, yes, that should be easy.