This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-20
Channels
- # announcements (5)
- # aws (15)
- # babashka (12)
- # beginners (87)
- # calva (13)
- # cider (16)
- # clj-kondo (4)
- # clojure (22)
- # clojure-argentina (1)
- # clojure-europe (9)
- # clojure-houston (1)
- # clojure-nl (2)
- # clojure-norway (25)
- # clojure-uk (5)
- # clojurescript (12)
- # core-typed (37)
- # cursive (15)
- # datomic (40)
- # editors (8)
- # emacs (4)
- # events (1)
- # hyperfiddle (29)
- # keechma (8)
- # leiningen (6)
- # lsp (7)
- # malli (25)
- # off-topic (26)
- # pathom (10)
- # portal (3)
- # re-frame (22)
- # reitit (1)
- # releases (1)
- # ring (2)
- # shadow-cljs (18)
- # yamlscript (1)
After adding my own function to completion-at-point-functions
it turns out that lsp-completion-at-point
shortcuts the completion function chain when it does not find any completions of its own. Is this intentional?
A completion at point-function can return nil
to pass on the completion, allowing the next completion function in line to try. I think maybe lsp-completion-at-point
always returns a lambda, which then would short-circuit the others in the list.
One way to work around that would be to ensure that lsp-mode appends instead of prepends to the list. Now it places itself in front of everything else.
It would be nice to get this fixed/changed. It feels a bit clunky to manually adjust the capfs if I want something like cape-file
to work when using LSP. I always assumed there must be some higher purpose for the existing behaviour 🙂