this is really cool @terry.poot I always hoped clojure-lsp could work with cljr too. cc @UKFSJSM38

@UKFSJSM38 and @U04V15CAJ have expressed that they want to support cljr, and are soliciting people to create issues for it. I don't have a lot of time right now, so if others want to help with that, it'd be great. And then we'll have real support and not my lame hack lol

Calva's default associations:

"languages": [
      {
        "id": "clojure",
        "aliases": [
          "Clojure",
          "clojure"
        ],
        "extensions": [
          ".clj",
          ".cljs",
          ".cljc",
          ".cljd",
          ".cljx",
          ".clojure",
          ".edn",
          ".joke",
          ".boot",
          ".bb",
          ".calva-repl"
        ],
        "configuration": "./language-configuration.json"
      }
    ],

I've asked if cljr users had any problems with clj-kondo a few years back and I got no responses :)

well, I wasn't one then 🙂

@terry.poot I'll give this a spin soon. @U04V15CAJ I need a primer on clj-kondo and how it works. Will engage over on that channel as I try to get up to speed. The CLR is the black sheep in the Clojure family obviously. But I have real reason to make Clojure a first class citizen on that platform (among them, preserving my sanity, as I have to work in both .NET and the JVM). That said, the problem with Clojure - the only problem I have with Clojure, really - is the tooling on all supported platforms is 100% pure Angus incidental complexity (IC). The language is relatively free of IC, but good grief the tooling... This is the only reason languages like Go, Rust, etc, take off: they get the tooling right out of the gate. Clojure has real challenge here, because it's kind of a slave of the tooling of the host environments to which it's by the bye ported and supported (and on it's best supported platform, there are three popular build systems...lol). So we all need to put our heads together and unify this sh*t. THEN and ONLY THEN, I think Clojure will be in a position to grab more developer mindshare.

The good news, at least with vsc/calva, is that clj-kondo and clojure-lsp are basically invisible. You don't have to learn anything out of the gate, only when you want to customize things.

Right now I've turned clojure-lsp off cuz my editor screen looked like Jeffrey Dahmer's basement when it was on. But hopefully with your fixes and a little finger grease (we don't really use our elbows when we type, do we?) I can enjoy a nice Chianti when I code. 🍷

If I didn't need a bunch of other things I can have for free with VS code (I do a lot with linked data, and RDF support in VS Code is light years ahead of Emacs and Vim), I would flip between cider and conjure. But most .NET devs whom I want to lure into Clojure are VS Code experienced, another reason to use Calva on the CLR.

Yeah, I used Intellij/Cursive for years, but the rest of my team is on VSCode, which is one of the main reasons I switched. And now I'm glad, because I wouldn't be able to hack Cursive, and last I heard, it had no support for cljr.

Plus, I'm a big fan of Calvados. (Why did they drop the DOS? Oh wait - nevermind)

I like Cursive, except for having to eat up half of my laptop memory just to edit files. 🙂

In my heart of hearts I want to be Vimmer. The Spartan life. Vim has Fennel via Lua now! (So much for being Spartan.) But then again, VS Code has ... Joyride. So whatever, man.

I just want to stop thinking about these things so I can focus on what I want to build. When I'm writing Clojure code, all is well. When I try to test, debug, interact with it, all of a sudden the smorgasbord of options eats up the void created by all the incidental complexity that the language removed from my life. LOL.

Tbf, I love all the options. But it definitely adds cognitive load that sometimes I wish I didn't have to carry. Such is life. 🙂

And the reality is, people building these tools are pouring their hearts and souls into them. So, seeing how they compete, compare, and each in their own way contribute to bettering the experience is fun to experience. But yeah, when the competition is fierce sometimes we have to accept that "no music will be played today" (Rich Hickey in one of his talks relating music to coding). 🙂

And right now on the CLR the Clojure music is hard to play. But it's worth playing there. Why? A lot of coders code (even live) there. As technologies go (set aside MS hatred, in which I am a fully vested member -- and really, is Oracle really better?), I am reminded of Leonard Cohen's "Anthem": Ring the bells that still can ring Forget your perfect offering There is a crack, a crack in everything That's how the light gets in

OK, I see it's time for bed. LOL.