This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-03
Channels
- # aleph (5)
- # announcements (4)
- # babashka (2)
- # beginners (52)
- # calva (13)
- # cider (60)
- # clj-kondo (91)
- # cljsrn (6)
- # clojure (93)
- # clojure-brasil (2)
- # clojure-dev (37)
- # clojure-europe (5)
- # clojure-italy (7)
- # clojure-nl (8)
- # clojure-norway (1)
- # clojure-sg (1)
- # clojure-spec (115)
- # clojure-uk (31)
- # clojurescript (32)
- # cursive (35)
- # data-science (4)
- # datascript (3)
- # datomic (29)
- # emacs (8)
- # events (1)
- # figwheel (1)
- # funcool (2)
- # graalvm (2)
- # joker (12)
- # kaocha (4)
- # lein-figwheel (1)
- # leiningen (34)
- # malli (7)
- # off-topic (4)
- # overtone (1)
- # parinfer (2)
- # pathom (5)
- # quil (1)
- # re-frame (12)
- # reagent (2)
- # shadow-cljs (7)
- # spacemacs (6)
- # sql (8)
- # tools-deps (63)
- # vim (24)
Thanks for the reports everyone, I’ve been trying to reproduce the logging error but haven’t been able to yet.
what is the last working combo? I have now 2019.2.3 & 190.eap2-2019.2 and the REPL doesn’t start. And how do I rollback to the last working combo?
@U055NJ5CC Go to https://plugins.jetbrains.com/plugin/8090-cursive/versions, choose EAP, download 1.9.0-eap1-2019.2 and then install from disk.
anyone else running project SDK java-1.8 have this problem?
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10)
OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)
maybe its irrelevant
I see many .jar files once I download an older version. Am I supposed to install all of them one by one?
that's strange, I see a single .zip
file cursive-1.9.0-eap1-2019.zip
with .jar files in it
maybe your zip ffile is getting automagically unpacked; you don't want that
@UFC2ETW9W Right, you want the original zip, IntelliJ will unpack it during the install process.
@cfleming is there a place with an overview with working Cursive x IntelliJ combos? Thanks!
Hi, I'm trying to use a debug REPL, I can set breakpoints and the debugger opens correctly, however whilst the debugger is paused, I can't evaluate any code in the REPL. I can't evaluate anything until I click continue. Hopefully this screenshot will explain it
Just a wild guess - what if you make the breakpoint to suspend only the current thread?
Note that even if that helps, it likely won't help in situations where a breakpoint was hit due to some code executed in the REPL input panel. Simply because it will be the same thread.
How would I make the breakpoint only suspend the current thread?
Sorry, found it, right clicking on the breakpoint show a menu that allows that.
@U2FRKM4TW I made that change but it still seems to have the same behaviour. Thanks for the suggestion though!
@U06790Y4E You can fire up another REPL window in a different thread. Or you can use a future
to run the command to be stopped in debugger.
@U0KD0N5T5 Thanks. If I fire up a different REPL it won't have access to to local variables as they currently are at the breakpoint. I thought this was a flow that I saw @cfleming use in his Debugging with Cursive video.
I use eval (alt-f8) to inspect. You can write clojure code there as well even though it is cumbersome.
Yes, Evaluate Expression is really the only way to do this right now. I have an idea that I should be able to detect if the debugger is paused for a particular REPL session, and if so then I should hopefully be able to use Evaluate Expression automatically, but I haven’t had time to investigate this properly.
@U06790Y4E check scope capture. Nice library to help debugging code: https://github.com/vvvvalvalval/scope-capture
Hm, I get Plugin 'Cursive' is incompatible with this installation trying to install cursive-1.9.0-eap1-2019.3.zip
from disk into IntelliJ IDEA 2019.2.3 (Ultimate Edition).
I've been bitten by the upgrade/downgrade cycle as the current Cursive/IntelliJ incompatibilities get worked out. When I downgrade, I've been moving the old .idea
directory out of the way to prevent version issues in settings. In doing so, (a) I end up losing my run configurations, (b) deps configuration (Cursive no longer recognizes the projects as deps projects) and (c) Cursive loses knowledge of some var resolutions it had before. I understand this is predictable result of reimporting the project. The part that I'm having the most issue with is the var resolution. Is this a stub regeneration issue? If so, how can I force stub regeneration? If not, what else might I need to look into?