This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-14
Channels
- # adventofcode (38)
- # announcements (42)
- # aws (3)
- # babashka (8)
- # beginners (165)
- # calva (36)
- # chlorine-clover (14)
- # cider (6)
- # clj-kondo (5)
- # cljsrn (33)
- # clojure (27)
- # clojure-australia (1)
- # clojure-czech (1)
- # clojure-doc (1)
- # clojure-europe (26)
- # clojure-nl (6)
- # clojure-spec (6)
- # clojure-uk (3)
- # clojurescript (10)
- # code-reviews (20)
- # conjure (1)
- # core-logic (5)
- # cursive (3)
- # data-science (5)
- # datomic (35)
- # emacs (1)
- # figwheel-main (3)
- # fulcro (10)
- # honeysql (1)
- # introduce-yourself (4)
- # jobs (3)
- # jobs-discuss (4)
- # minecraft (2)
- # missionary (28)
- # nextjournal (3)
- # off-topic (45)
- # pathom (7)
- # polylith (1)
- # portal (22)
- # practicalli (2)
- # re-frame (4)
- # reagent (19)
- # releases (3)
- # remote-jobs (3)
- # reveal (1)
- # rum (4)
- # shadow-cljs (37)
- # spacemacs (14)
- # sql (1)
- # tools-build (7)
- # tools-deps (16)
- # vim (13)
- # xtdb (15)
About once a month I give a try to LSP in Spacemacs and get bummed that it impolitely overrides CIDER's behavior with describe-thing-at-point
and cursor hover 😞
Have you raised an issue on the Spacemacs repository about this?
I don't have an issue with this binding as I find the other help bindings more useful. I can also get docs from auto-complete and LSP UI doc popups. Feel free to suggest some alternative key bindings to the Spacemacs mainteners, or rebind keys in the dotspacacs/user-config
Is this one key binding definition in the Clojure layer your only concern?
not just the key binding, also the display at the bottom frame when the cursor hovers over symbols
I only recall that one changed key binding. LSP does add its own keybindings along side the Cider and clj-refactor key bindings (I have used clj-refactor for years, so theyay be some over-riding there)
Presumably
"hh" 'cider-doc
"=r" 'cider-format-region
"ge" 'cider-jump-to-compilation-error
"gr" 'cider-find-resource
"gs" 'cider-browse-spec
"gS" 'cider-browse-spec-all))
LSP by nature adds a lot of common language features, some of which CIDER also implemented. They are both self-described IDEs so bound to be some crossover. LSP is a big change to Emacs UI (although more features in the UI are now switched off by default). Unless there are specific LSP features needed, stick with Cider and clj-kondo
I'm very happy with cider, mostly concerned I might be missing something by not using LSP too
Take a look at the features guide to see if you really need LSP https://emacs-lsp.github.io/lsp-mode/tutorials/clojure-guide/#lsp-features
If you do try LSP, then it would also be worth looking at how to enable/disable specific features https://emacs-lsp.github.io/lsp-mode/tutorials/how-to-turn-off/