This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-30
Channels
- # adventofcode (7)
- # announcements (9)
- # babashka (20)
- # beginners (182)
- # calva (9)
- # cider (20)
- # circleci (3)
- # clj-kondo (1)
- # clojure (269)
- # clojure-europe (2)
- # clojure-india (1)
- # clojure-italy (6)
- # clojure-nl (5)
- # clojure-uk (50)
- # clojurescript (56)
- # code-reviews (3)
- # core-async (174)
- # datomic (4)
- # duct (1)
- # emacs (3)
- # events (1)
- # fulcro (31)
- # graalvm (10)
- # graphql (8)
- # jobs (1)
- # joker (11)
- # juxt (7)
- # luminus (2)
- # malli (4)
- # off-topic (2)
- # overtone (1)
- # pathom (2)
- # re-frame (24)
- # shadow-cljs (42)
- # sql (1)
- # tools-deps (10)
@nirrub I believe that cider-find-var
only works when the REPL is running and the code you are trying to find is evaluated. I rarely use this function myself as it doesn’t feel very reliable.
I use symbol highlighting (a Spacemacs transient state, not sure if it’s in Doom, sorry).
Or I use helm-ag or swoop to jump to symbol locations in a buffer or project, using narrowing to a function if relevant. There are quite a few Emacs approaches to finding things.
To refactor a local binding name, I use iedit and narrowing if the local binding name is not unique to the function in that namespace.
Here are various ways I have learned to navigate code
https://practicalli.github.io/spacemacs/navigating-code/
I haven’t used Doom, but assume if the same packages are installed then you can do the same things as I do in Spacemacs.