Fork me on GitHub
just.sultanov01:04:24 - a project management tool. The current features: - Unify a project manifest - Collect dynamic metadata of builds at compile time (e.g. uberjar step) and use the metadata at runtime - Transform a project manifest to io.github.seancorfield/build-clj format - Manage project version

Jakub Holý (HolyJak)13:04:17

Hi @U1EQNSHL4! Congratulation to the release! Personally, I would appreciate a brief section explaining the problem the library tries to solve so that I would understand better whether it is something for me and when/why I would want to use it 😅

☝️ 2
kingmob08:04:19 is out, with better support for Graal and clj-easy and an updated Manifold dep. To avoid problems with Graal/clj-easy, all code has been copied out of the top-level single-segment namespace to a nested namespace, and the original top-level ns has been deprecated. Many thanks to @craigy for doing this and @p2b for bringing up the issue.

🎉 7
👀 1

Announcing new lib, a lib that should help create any LSP for any language in Clojure 🎉 This was a result of a refactor on clojure-lsp side, separating the common server code to make that possible. Thanks @domagala.lukas for the great help of making that possible!

🎉 22
👏 7


😂 2
🥥 1
🦈 1

Just to clarify, could I use this to start a TCP lsp server? Then use the nrepl/orchard stuff to handle things like completion?


probably not, this follows Microsoft LSP spec which say the connection should be via stdin/stdout


Is that distinct from the official LSP spec, which does allow for TCP? (or at least, did?)


> Servers usually support different communication channels (e.g. stdio, pipes, …). To ease the usage of servers in different clients it is highly recommended that a server implementation supports the following command line arguments to pick the communication channel: > • stdio: uses stdio as the communication channel. > • pipe: use pipes (Windows) or socket files (Linux, Mac) as the communication channel. The pipe / socket file name is passed as the next arg or with --pipe=. > • socket: uses a socket as the communication channel. The port is passed as next arg or with --port=. > • node-ipc: use node IPC communication between the client and the server. This is only support if both client and server run under node. From


Oh, you are right! I missed that, ATM lsp4clj only supports stdio, but we could add support for others. Although, I don't see TCP, would socket suppress that need?

Lukas Domagala00:04:36

I also assumed stdio was the only option. Node-ipc is probably out since we’re JVM only for now, but socket should be possible. Websocket seems to also be an option, but it needs a bunch of extra setup: Looking at issue it seems that the LSP server actually has to connect to the client, which is a bit weird, but probably doable.

👍 1

TCP and socket are the same.


Feel free to open a issue there @U09LZR36F!

Asko Nōmm19:04:34 1.1 - An extensible and modular zero-dependency, pure-Clojure Markdown parser. Improvements: • Support setext headings • Make text emphasis better • Add full test coverage • Support triple-dash (`---`) horizontal lines • Support dash (`-`) unordered lists Bug fixes: • Underscores in link URL’s get rendered into <em>’s • Links break textual checkboxes

🎉 16
Vincent Cantin10:04:10

We (admins) recommend that updates of libraries recently announced should be published in #releases instead.

Asko Nōmm18:04:31

Oh sweet! Will join that 🙂