This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-16
Channels
- # babashka (48)
- # beginners (72)
- # calva (65)
- # cider (10)
- # clerk (11)
- # clj-kondo (14)
- # clojure (85)
- # clojure-austin (11)
- # clojure-czech (1)
- # clojure-europe (26)
- # clojure-nl (1)
- # clojure-uk (6)
- # core-matrix (1)
- # cursive (8)
- # datomic (20)
- # docker (38)
- # emacs (2)
- # events (1)
- # fulcro (6)
- # funcool (6)
- # hyperfiddle (79)
- # introduce-yourself (1)
- # lsp (131)
- # malli (32)
- # off-topic (11)
- # pathom (3)
- # re-frame (11)
- # reagent (15)
- # releases (2)
- # shadow-cljs (49)
- # sql (3)
- # tools-deps (36)
cider-apropos
uses completing-read, but it's not handled by vertico ~corfu~
for some reason. Any of you got that combo working?
So, cider-apropos-select
and then hitting RET
will actually do what I want. I can then interactively narrow to the function I'm interested in. Kind of weird behavior TBH. Would be much better to just skip the RET
and start filtering immediately
I guess there are performance implications, but at least on this pc it is pretty much instant
See this for context https://github.com/clojure-emacs/cider/issues/1541
I get that, but shouldn't the cider-apropos-select just start with the completing read, so that you can just start typing and narrow your search without having to supply an empty query first?
Ah, you mean this. I guess it was just done to be consistent with the other command. But also otherwise we’d have to dump every symbol that’s currently known which is going to be pretty slow.
Here's some cider/nrepl middleware I just made https://github.com/drcode/nrepl-gpt