This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-25
Channels
- # arachne (1)
- # beginners (22)
- # boot (21)
- # cider (23)
- # cljs-dev (16)
- # cljsrn (9)
- # clojure (118)
- # clojure-dev (11)
- # clojure-greece (16)
- # clojure-italy (10)
- # clojure-losangeles (4)
- # clojure-russia (14)
- # clojure-serbia (4)
- # clojure-spec (58)
- # clojure-uk (33)
- # clojurescript (30)
- # cursive (17)
- # datomic (48)
- # docs (22)
- # events (1)
- # fulcro (24)
- # hoplon (3)
- # jobs (6)
- # jobs-discuss (4)
- # keechma (4)
- # leiningen (11)
- # luminus (4)
- # midje (1)
- # off-topic (107)
- # onyx (30)
- # other-languages (12)
- # pedestal (4)
- # re-frame (72)
- # reagent (6)
- # remote-jobs (1)
- # shadow-cljs (16)
- # spacemacs (3)
- # specter (9)
- # uncomplicate (4)
- # unrepl (40)
Is there a way to teach cursive about bindings from clojure.core.match
? For me, it shows the bound variables from patterns as cannot be resolved
@nblumoe often wondered the same thing, using core.match leaves little yellow failed inspection turds all over my buffer :)
@nblumoe there is a way to say to cursive that this macro behaves like one it knows about (`let`?)
It involves editing an internal config file somewhere, I can’t remember where though
Thanks, I just checked the light bulb menu and indeed one can make it “resolve as let
“. But that alone doesn’t help apparently. Not sure if any of the options will. But this might be the way to go. Investigating….
I am afraid, this won’t cover match
and the following applies: "This support will work in a lot of cases, but we’ll be adding more sophisticated support soon to allow users to help Cursive understand more complicated forms."
There is the “Specify…” option which I don’t quite understand. Maybe @cfleming could quickly explain it. Seems not to be covered in the docs (yet)
@nblumoe is there another form that is closer to the macro? The undocumented part is that you can hack an internal file to make it match any macro, not just the five that are specified
@danielcompton @nblumoe Yeah, sadly Cursive doesn’t understand anything that looks like core.match.
I’ll see if I can add support soon, it’s a library I’ve been meaning to support for a while now.
@hiskennyness No, that sounds very strange, and very hard to reproduce.
@wilkerlucio Try Appearance & Behavior->System settings->Synchronise files on frame deactivation
If you turn that off you may have to manually synchronise a fair bit when files have changed.
thanks, I think that works 🙂