This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-17
Channels
- # announcements (4)
- # beginners (82)
- # boot (1)
- # calva (26)
- # cider (13)
- # clj-kondo (41)
- # cljs-dev (25)
- # cljsrn (7)
- # clojure (82)
- # clojure-berlin (1)
- # clojure-brasil (1)
- # clojure-dev (13)
- # clojure-europe (11)
- # clojure-italy (27)
- # clojure-nl (8)
- # clojure-russia (6)
- # clojure-spec (32)
- # clojure-uk (15)
- # clojurescript (61)
- # core-async (1)
- # cursive (9)
- # data-science (1)
- # datomic (18)
- # duct (1)
- # emacs (2)
- # events (7)
- # fulcro (13)
- # graalvm (5)
- # immutant (1)
- # jobs-discuss (63)
- # leiningen (3)
- # off-topic (48)
- # om (3)
- # pathom (13)
- # planck (20)
- # prelude (3)
- # re-frame (55)
- # reagent (13)
- # reitit (5)
- # rewrite-clj (12)
- # shadow-cljs (67)
- # spacemacs (14)
- # sql (5)
- # tools-deps (4)
- # vim (23)
- # yada (2)
ctrl+click'ing on keywords used to open the "Usages of ..." window inline. This still works for function symbols but it is not working for keywords. I'm on v1.8.2-eap4-2019.1.
I'm trying to the REPL like I normally do, but I'm getting this error: > Error running 'REPL': Error executing Leiningen configuration. Are there more logs that I can pull up and see what the issue is? REPL works fine on a different Clojure project.
I switched the run configuration to this:
All is good now, is this expected?
Ok, another update, it seems like it was an issue with having uncompiled Java files. lein javac then running the REPL using "Run with Leiningen" got me back to desired state.
@U0JAE119P That’s very weird, though. I’m not sure what might have been going on there. The best log to look in is Help | Show log in Finder/Explorer, but lein doesn’t always return much useful information to put in there.
I did that, but there weren't any logs regarding the error 😞 That error had me going for a while and I couldn't figure out what it was. If there's anything I can do to pinpoint the issue let me know and I can file a more extensive bug report (if it is indeed a bug).