This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-24
Channels
- # aleph (19)
- # announcements (59)
- # asami (34)
- # aws (1)
- # babashka (17)
- # beginners (174)
- # bitcoin (11)
- # calva (16)
- # chlorine-clover (5)
- # cider (5)
- # clj-kondo (14)
- # cljsrn (13)
- # clojars (25)
- # clojure (124)
- # clojure-australia (1)
- # clojure-europe (48)
- # clojure-nl (4)
- # clojure-spec (1)
- # clojure-uk (40)
- # conjure (6)
- # core-async (25)
- # cursive (30)
- # data-oriented-programming (3)
- # datomic (14)
- # depstar (14)
- # emacs (3)
- # graalvm (27)
- # helix (1)
- # honeysql (25)
- # hoplon (3)
- # jobs-discuss (6)
- # kaocha (3)
- # lsp (109)
- # lumo (1)
- # malli (5)
- # meander (21)
- # music (1)
- # pathom (1)
- # re-frame (4)
- # reitit (1)
- # remote-jobs (1)
- # reveal (11)
- # rewrite-clj (3)
- # shadow-cljs (42)
- # spacemacs (15)
- # sql (13)
- # startup-in-a-month (4)
- # tools-deps (45)
- # vim (16)
- # xtdb (23)
- # yada (1)
Is there a way to jump to the "code at point" from the stacktrace printed in the REPL buffer using a keyboard shortcut?
I'm using spacemacs and , g d
(should be the same thing as cider-find-var
) works most of the time but not here - but mouse click works (opens the code in another buffer).
You can actually interrogate emacs for this information C-h k (mouseclick)
in the stacktrace buffer should tell you which function is called. Then check C-h m
in the stacktrace buffer to see all key maps active in that buffer (so that you can see if something conflicts with ,gd
)
Then bind ,gd
to do what you want
This confused me as well, I expected RET
to work but it did not (probably because of something else in my setup)