This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-22
Channels
- # announcements (16)
- # babashka (7)
- # babashka-sci-dev (14)
- # beginners (34)
- # calva (80)
- # clj-kondo (23)
- # cljdoc (17)
- # cljs-dev (1)
- # cljsrn (10)
- # clojure (51)
- # clojure-berlin (3)
- # clojure-europe (14)
- # clojure-italy (10)
- # clojure-nl (2)
- # clojure-norway (211)
- # clojure-uk (5)
- # clojurescript (4)
- # cursive (22)
- # datalevin (12)
- # datomic (2)
- # defnpodcast (1)
- # duct (5)
- # emacs (4)
- # events (2)
- # fulcro (3)
- # graalvm (1)
- # interop (3)
- # introduce-yourself (4)
- # java (1)
- # jobs (7)
- # kaocha (38)
- # leiningen (3)
- # lsp (11)
- # malli (4)
- # membrane (5)
- # music (1)
- # off-topic (28)
- # pathom (13)
- # pedestal (3)
- # polylith (4)
- # portal (10)
- # practicalli (1)
- # re-frame (33)
- # reitit (2)
- # remote-jobs (1)
- # sci (6)
- # shadow-cljs (49)
- # sql (4)
- # xtdb (3)
I just wanted to stop in and say that I came back to clojure recently and played around a bit with cursive. I was able to get a debugger repl running and play around inside some toy functions and eventually I plan to be more comfortable using a repl driven development style. In the meantime, as a novice, having access the the intellji debugger is a much welcome feature that makes becoming more familiar with the dev enviroment a much smoother process. Thank you for your work @cfleming!
Thanks for the kind words! I’m glad Cursive is helping to make Clojure more accessible for you. That’s one of my major goals.
I’m still periodically getting custom macros that are not resolved like I specified them to be. The work-around here is to resolve as def
and then resolve as defn
again. It’s like Cursive is losing the context of those custom macros resolutions
Built on: 2022-02-24 09:26
Built from: 1.12.2-eap6-13-g96b19682
fwiw, I see the same issue. Seemingly randomly cursive (or intellij?) seems to forget custom macros. I resolve the problem by doing the same thing
I have not tried in CLJS
Ok thanks, a few people reported that it was more prevalent in CLJS, but that may have just been chance.
When this occurs, could you check in Preferences | Languages & Frameworks | Clojure | Symbol Resolution and see if the macro in question is still present there in the configuration? It would be interesting to know if it’s failing despite the config being present, or if the config is falling off somehow.
Sure. I'll take a look at that next time
I’d also like to know if this only happens for a single macro at a time, or if it suddenly appears to lose customisations for all macros.
I have this happen in CLJS fairly often. I'll take a look in the preferences area next time around. Thanks!
Here's a case. You'll see that mount's defstate is not resolving correctly
But it is in the symbol resolution table:
The meander macros are handled correctly in the same file
Yeah, hey! I just had this fail again this morning and am seeing the same thing as @U2845S9KL. It’s not resolving even though it is declared as such
Hey, just tried out the babashka repl in Cursive. Love it! One question, though. When I set environment variables in the run config they don’t seem to be getting set when I call (System/getenv). Is this a bug? E.g.
Then in the repl: