This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-18
Channels
- # ai (1)
- # beginners (71)
- # boot (15)
- # cider (26)
- # clara (4)
- # cljs-dev (81)
- # cljsrn (26)
- # clojure (393)
- # clojure-berlin (2)
- # clojure-dev (5)
- # clojure-dusseldorf (1)
- # clojure-greece (5)
- # clojure-italy (6)
- # clojure-russia (97)
- # clojure-serbia (11)
- # clojure-sg (2)
- # clojure-spec (14)
- # clojure-uk (66)
- # clojurescript (58)
- # core-async (19)
- # cursive (18)
- # data-science (2)
- # datomic (75)
- # emacs (20)
- # events (5)
- # figwheel (1)
- # graphql (2)
- # hoplon (29)
- # jobs-discuss (3)
- # juxt (6)
- # lein-figwheel (1)
- # london-clojurians (2)
- # lumo (29)
- # mount (9)
- # off-topic (4)
- # om (16)
- # onyx (25)
- # other-languages (2)
- # pedestal (38)
- # protorepl (2)
- # re-frame (20)
- # reagent (9)
- # ring-swagger (6)
- # sql (10)
- # unrepl (3)
- # untangled (19)
- # utah-clojurians (1)
- # videos (2)
- # vim (20)
They are the only analysis warnings I have left in a couple of files, I'd love to get rid of them.
@wilkerlucio Good idea, can you file an issue for that?
@nwjsmith It might be that Specter defines that using a macro or some other trickery.
@souenzzo @timgilbert Could you try this: Go to Help->Debug Log Settings… and enter cursive.stubs
into the box. Then reproduce the problem, and send me the log from Help->Show log in Finder/Explorer by email to <mailto:[email protected]|[email protected]>?
@cfleming cool, issue created: https://github.com/cursive-ide/cursive/issues/1755
@cfleming: I was able to fix it via File / Invalidate Caches
Now I can't reproduce but I'll shoot you a debug log if I do
@rafael Sadly not yet, but that will be coming soon (like, the next couple of releases).
In the meantime you can use https://github.com/mfikes/tubular as a workaround.
My current use case is probably not very generalizable, I think. I'm running a gorilla repl in docker and I'd also like to connect Cursive to it, but it binds nrepl to localhost
which cannot be exposed outside of the container. I thought of working around it with the socket repl, but I'll find another workaround.