This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-26
Channels
- # announcements (7)
- # babashka (42)
- # beginners (349)
- # chlorine-clover (9)
- # cider (16)
- # circleci (2)
- # clj-kondo (6)
- # cljs-dev (61)
- # cljsrn (15)
- # clojure (95)
- # clojure-europe (11)
- # clojure-italy (2)
- # clojure-nl (4)
- # clojure-spec (4)
- # clojure-uk (24)
- # clojurescript (21)
- # conjure (2)
- # core-async (8)
- # cursive (12)
- # datascript (2)
- # emacs (4)
- # exercism (1)
- # figwheel-main (86)
- # fulcro (27)
- # graalvm (4)
- # helix (36)
- # hoplon (3)
- # interop (44)
- # kaocha (6)
- # lein-figwheel (4)
- # malli (7)
- # meander (9)
- # off-topic (95)
- # pathom (33)
- # pedestal (13)
- # re-frame (20)
- # reitit (3)
- # shadow-cljs (102)
- # tools-deps (14)
- # xtdb (16)
Is it just me that finds the behaviour of Ctrl + Left/Right
within a string to be counter-intuitive?
@U0FR9C8RZ , you should give this a thumbs up vote so Colin knows that other people are having issues with this 🙂
Is anyone else getting an issue with remote repls where if you get a REPL command timeout the repl just seems to timeout in general?
I've noticed that this statement produces an inspection warning that VERSION cannot be resolved:
(defonce ^:const VERSION "0.0.1")
However this statement has no issue:
(def ^:const VERSION "0.0.1")
Is this a Cursive issue?Yes, that's https://github.com/cursive-ide/cursive/issues/1069. I just took a look at this, I'll fix it for the next EAP.
Gotcha. I'm still learning what's IntelliJ and what's Cursive, the integration is so nice it's hard to tell where one end and the other begins. I found that I'm getting lots of the same "cannot resolve" when I use manifold.deferred/let-flow, which is a macro that behaves like let.
Yeah, you can fix that using this: https://cursive-ide.com/userguide/macros.html#customising-symbol-resolution
BEST TIP EVER!!! That just fixed so many non-problems from being flagged. Thank you!!