This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-13
Channels
- # aleph (16)
- # announcements (8)
- # aws (5)
- # babashka (54)
- # beginners (48)
- # calva (7)
- # cider (7)
- # clojure (209)
- # clojure-brasil (4)
- # clojure-europe (20)
- # clojure-italy (12)
- # clojure-nl (21)
- # clojure-uk (69)
- # clojurescript (24)
- # cursive (11)
- # datascript (7)
- # datomic (47)
- # emacs (14)
- # graphql (20)
- # hoplon (25)
- # jobs (1)
- # kaocha (1)
- # leiningen (14)
- # meander (7)
- # off-topic (44)
- # other-languages (1)
- # pathom (20)
- # re-frame (2)
- # reagent (51)
- # reitit (3)
- # remote-jobs (1)
- # shadow-cljs (46)
- # spacemacs (5)
- # sql (65)
- # tools-deps (86)
- # vim (11)
Here’s a question… I’m using CIDER to connect to an older project running the older figwheel. It starts up, seems to work fine, but then in the minibuffer, I see a prompt Stdin:
that never seems to go away.
It seems to echo the input into the REPL prompt.
That’s the cljs repl behavior without figwheel. It’s asking for standard in (the R in REPL) without middleware of piggieback
What is the procedure for making Cider aware of the javadoc for a non-standard java library? cider-javadoc
works out of the box for things like java.util.Date
, but not for libraries that I have imported from Maven
thanks, that helps!