This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-31
Channels
- # announcements (8)
- # babashka (8)
- # beginners (13)
- # biff (1)
- # calva (1)
- # cider (12)
- # clj-kondo (16)
- # cljs-dev (3)
- # cljsrn (14)
- # clojure (18)
- # clojure-austin (2)
- # clojure-czech (3)
- # clojure-europe (54)
- # clojure-germany (5)
- # clojure-nl (1)
- # clojure-norway (2)
- # clojure-spec (4)
- # clojure-survey (2)
- # clojure-uk (1)
- # clojured (15)
- # clojurescript (5)
- # conjure (6)
- # core-async (65)
- # cursive (24)
- # data-science (1)
- # emacs (9)
- # events (3)
- # graphql (5)
- # integrant (6)
- # jobs (2)
- # joyride (62)
- # lsp (5)
- # malli (10)
- # off-topic (20)
- # pathom (57)
- # polylith (18)
- # re-frame (12)
- # remote-jobs (3)
- # rewrite-clj (14)
- # sci (2)
- # shadow-cljs (41)
- # sql (9)
- # tools-deps (68)
It works well, except for navigating to external deps code, which does not work at all. Issue mapped here: https://github.com/joaotavora/eglot/issues/661
This does not bother me much because I can use clojure.repl/source
or consult the source directly, since it’s mostly a lib from my company anyways
@U976F1AR2 what would you say are the advantages of using eglot over clojure-lsp for clojure?
I don’t see any advantage specifically for Clojure. I like eglot
because it feels very emacsy.
When I used lsp-mode
, I had to disable some stuff in order to make it more visually pleasant, and I found it to be more noisy (for example, it warned about not finding flycheck or company, which I don’t use anyway). eglot
just works as I want w/o configuration.