This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-20
Channels
- # adventofcode (38)
- # announcements (8)
- # aws (4)
- # babashka (131)
- # beginners (263)
- # calva (2)
- # clj-kondo (12)
- # cljdoc (12)
- # cljsrn (3)
- # clojure (122)
- # clojure-europe (3)
- # clojure-finland (2)
- # clojure-nl (13)
- # clojure-uk (80)
- # clojured (1)
- # clojuredesign-podcast (3)
- # clojurescript (78)
- # core-async (19)
- # cursive (19)
- # datomic (7)
- # duct (10)
- # events (1)
- # fulcro (7)
- # graalvm (12)
- # graphql (3)
- # juxt (4)
- # malli (10)
- # music (3)
- # nrepl (4)
- # off-topic (25)
- # pathom (4)
- # pedestal (1)
- # re-frame (78)
- # reagent (8)
- # shadow-cljs (91)
- # sql (8)
- # vim (3)
- # xtdb (2)
I'm running a old-ish version of IntelliJ and cursive (2018.3.6 + cursive v1.8.1-eap3-2018.3) with deps.edn (as for some time this version was the most stable with deps.edn). It seems that something is wrong with resolving the vars in cljs files
Is clojurescript added to the module as a dependency? You can check that under File->Project Structure->Modules-><your module>->Dependencies
Interesting. Ok, so if you switch back to the git dep, what does the library look like? When you select the library in File->Project Structure->Libraries, what do you see in the right hand panel?
even defn
cannot be resolved. Whereas in clj
files it all works fine. i tried to invalidate the cache and restart multiple times, to no avail
@cfleming: Will b 11
be moved up as in out of the binding box, or up a line, or up as in front of whatever pair is before it? (Or something else? 😃 )
It works basically like “Move form up/down”, so if you move it up, you’ll get:
(let [|b 11
a 10])
Then trying to move it up again will do nothing - it doesn’t work like slurp/barf.Mind if I ask what conversation this thread forked from? I saw your reply to @UFHE11C83 yesterday and I'd be interested in the context.
@U08BJGV6E: It's from here (I think): https://clojurians.slack.com/archives/C17JYSA3H/p1576786762006900
I’ve filed that this behaviour should be added to Calva as a feature request: https://github.com/BetterThanTomorrow/calva/issues/529