This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-04
Channels
- # announcements (5)
- # babashka (2)
- # beginners (53)
- # biff (11)
- # calva (5)
- # cider (4)
- # clojure (32)
- # clojure-austin (2)
- # clojure-dev (5)
- # clojure-europe (17)
- # clojure-norway (22)
- # clojurescript (23)
- # core-logic (1)
- # cryogen (1)
- # datomic (1)
- # dev-tooling (7)
- # emacs (6)
- # fulcro (63)
- # guix (1)
- # hyperfiddle (14)
- # integrant (2)
- # lsp (6)
- # missionary (4)
- # nbb (42)
- # overtone (9)
- # reitit (8)
- # specter (3)
- # sql (2)
- # squint (7)
- # tools-build (9)
compliment-lite is a trimmed-down single-file version of Compliment, Clojure's most gallant completion library. If you need to implement code completion in your project and, for any reason, don't want to add a dependency on Compliment, consider picking compliment-lite. It supports most completions that Compliment provides: vars, namespaces, classes, static and non-static class members, keywords. See https://github.com/alexander-yakushev/compliment/tree/master/lite.
Forgive a really, really naive question for the curious newbies - I see Compliment is written in Clojure. How do Emacs, VSCode and the rest execute it? How would my hypothetical new doubleplusgood editor use it? š¬š
It is a valid question! Emacs Clojure IDE called CIDER has a "frontend" part, written in Emacs Lisp, which lives in the editor, and the "backend" part, called cider-nrepl, written in Clojure. The backend part is injected into the application you are currently working on and have a REPL of it running. In case of VSCode, I think it also uses cider-nrepl as the IDE backend. This is the similar concept to LSP; however, LSP implementations usually run in a separate process, whereas Clojure IDE backends such as cider-nrepl run within the same process as the application being developed.