This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-10
Channels
- # announcements (16)
- # asami (7)
- # aws (5)
- # beginners (46)
- # calva (47)
- # clj-kondo (3)
- # cljdoc (23)
- # clojure (70)
- # clojure-germany (1)
- # clojurescript (6)
- # community-development (2)
- # datomic (3)
- # emacs (14)
- # exercism (5)
- # hyperfiddle (4)
- # jobs (1)
- # kaocha (9)
- # lsp (13)
- # malli (6)
- # membrane (11)
- # off-topic (22)
- # pedestal (4)
- # portal (19)
- # quil (3)
- # reagent (8)
- # remote-jobs (1)
- # shadow-cljs (48)
- # spacemacs (5)
https://github.com/lazy-cat-io/tools.project - 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
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 😅
https://clojars.org/org.clj-commons/byte-streams 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.
Announcing new lib https://github.com/clojure-lsp/lsp4clj, 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!
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 https://microsoft.github.io/language-server-protocol/specifications/specification-current/
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?
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: https://github.com/microsoft/vscode/blob/main/src/vs/base/parts/ipc/node/ipc.net.ts#L184-L431 Looking at https://github.com/microsoft/language-server-protocol/issues/604 issue it seems that the LSP server actually has to connect to the client, which is a bit weird, but probably doable.
Feel free to open a issue there @U09LZR36F!
https://github.com/askonomm/clarktown 1.1 - An extensible and modular zero-dependency, pure-Clojure Markdown parser.
Improvements:
• Support setext headings https://github.com/askonomm/clarktown/issues/6
• Make text emphasis better https://github.com/askonomm/clarktown/issues/5
• Add full test coverage https://github.com/askonomm/clarktown/issues/4
• Support triple-dash (`---`) horizontal lines https://github.com/askonomm/clarktown/issues/10
• Support dash (`-`) unordered lists https://github.com/askonomm/clarktown/issues/11
Bug fixes:
• Underscores in link URL’s get rendered into <em>’s https://github.com/askonomm/clarktown/issues/9
• Links break textual checkboxes https://github.com/askonomm/clarktown/issues/8
We (admins) recommend that updates of libraries recently announced should be published in #releases instead.