Clojurians Log v2

You can run Clojure LSP with a JVM, I do all the time

Search for clojure-lsp-dev and you’ll find my snippet

Ah, here: https://github.com/clj-kondo/clj-kondo/blob/master/doc/editor-integration.md got it. Thanks!

It seems like in build.clj, even debug builds are created with an AOT build? This would work with a normal JVM, of course, since it's just class files. But since Flowstorm works by (as I understand it!) instrumenting .clj files as they are compiled into classes, the AOT part causes a problem with that instrumentation. At least that's how I think it's working. I'm still experimenting as I'm writing it up. I was thinking of creating a PR with some updates to development.md with extra info for debugging and code coverage.

humm I see, didn't know AOT could affect that

sure, go ahead!

I submitted https://github.com/clojure-lsp/clojure-lsp/pull/2432 . I was trying to decide if this needed a new page, but I'm leaning to it's easier to deal with in development.md. It's also possible to add the changes mentioned in the code directly into clojure-lsp - it would make some things like Flowstorm visualizers easier, but I figure it's better to wait on that to see if Flowstorm is more generally useful first.

aswesome, loved the images! not sure you know you can test with bb local-webpage to see the docs compiled

Oh, I didn't know that! I was just using the md preview

yeah it should work md preview, but this way you can really see how it looks like http://clojure-lsp.io, sometimes there is some weird alignment or something you could try something else

for example, instead of <details> you can use === from mkdocs material support, similar how I did in ECA https://github.com/editor-code-assistant/eca/blob/fa275b16ae42abacbc720e91d4921ccec6b45e27/docs/read-chat.md?plain=1#L85, but just in case yours didn't look good

it renders nice collapsable sections

everything looks good to me, BTW if you wanna add a alias for clofidence in deps.edn I'm pretty ok with that, so docs may be simpler and out of the box

I like the idea of it working out of the box - it might get more use. But I was thinking as an interim solution just add the documentation. If we think it makes sense to add it into the code, that's easy enough (and I can modify the docs too)

Hm... I think I need a newer version of docker

sure, your call!

yeah, also not sure if we should bump mkdocs in https://github.com/editor-code-assistant/eca/blob/fa275b16ae42abacbc720e91d4921ccec6b45e27/docs/read-chat.md?plain=1#L85 repo, I believe so, I needed to do in http://eca.dev as well to have latest fixes/nice ux, but something for later