This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-31
Channels
- # announcements (20)
- # asami (14)
- # aws (6)
- # babashka (15)
- # beginners (83)
- # biff (6)
- # calva (93)
- # cider (3)
- # clj-kondo (21)
- # cljdoc (106)
- # cljs-dev (32)
- # clojure (165)
- # clojure-dev (78)
- # clojure-europe (54)
- # clojure-italy (9)
- # clojure-nl (9)
- # clojure-norway (24)
- # clojure-uk (4)
- # clojurescript (6)
- # community-development (2)
- # conjure (2)
- # core-typed (14)
- # datahike (4)
- # datomic (2)
- # emacs (40)
- # events (1)
- # fulcro (11)
- # graalvm-mobile (29)
- # graphql (8)
- # honeysql (19)
- # java (1)
- # jobs (1)
- # lsp (232)
- # malli (5)
- # membrane (112)
- # nextjournal (11)
- # off-topic (63)
- # portal (12)
- # re-frame (6)
- # reagent (3)
- # reitit (4)
- # rewrite-clj (2)
- # shadow-cljs (25)
- # tools-deps (6)
Would it be a good idea to add a variable like cider-clojure-cli-aliases which has a different scope?
My use case: I wish to define global development convenience aliases I'll start with by default, and dir-local aliases for specific projects
So that would translate to something like cider-clojure-cli-aliases and cider-clojure-global-cli-aliases
I just got bit by this last night - started a new project, hacked away for a while, added a dependency, restarted the repl and boom! - the dependency wasn't on the classpath! I spent a good 20 minutes scratching my head before realizing I didn't have a dir-locals file that added the :dev alias to my repl command : / This happens to me about every 3 months or so.
Hey, so is it a known issue that the cider debugger compiles symbols in function call position as from clojure.core even when that symbol is shadowed by a local binding?