This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-26
Channels
- # announcements (3)
- # architecture (53)
- # babashka (6)
- # beginners (101)
- # bitcoin (3)
- # calva (4)
- # cider (3)
- # clara (7)
- # cljdoc (2)
- # cljsrn (14)
- # clojure (104)
- # clojure-europe (96)
- # clojure-germany (21)
- # clojure-nl (6)
- # clojure-serbia (3)
- # clojure-spain (1)
- # clojure-uk (13)
- # clojuredesign-podcast (4)
- # clojurescript (14)
- # cursive (5)
- # data-science (19)
- # datomic (16)
- # emacs (15)
- # fulcro (33)
- # graalvm (5)
- # honeysql (3)
- # instaparse (2)
- # jobs (3)
- # lsp (82)
- # malli (2)
- # off-topic (11)
- # pedestal (4)
- # polylith (62)
- # practicalli (4)
- # shadow-cljs (56)
- # tools-deps (53)
- # vim (17)
- # xtdb (53)
Hi! Has anyone tried neovim 5 with closure-lsp? Using nvim-lspconfig
no coc-nvim.
yeah but it looks like they normally use Emacs
thanks anyway
@aldo.nievas I gave that a try this week, but didn't really have time to get the setup just right. So for now I'm back on coc.nvim+clojure-lsp
yes there is a thread on #lsp about that. Looks like a minor issue.
yeah just wanted to make sure you were aware of that channel
Something I really liked from the nvim-lsp config is vim.lsp.buf.signature_help()
. I still want to see if there's a (coc-signature-help)
or some such, but haven't got around to that yet
If nothing else, this exercise at least taught me more about LSP and the functionality that clojure-lsp supports. I'm still a bit confused where all the functionality boundaries are between Conjure and coc.nvim, and ALE is mixed in there too 😵. Hopefully I can spend a bit more time on this over the weekend.