Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-04-20

Channels

#cursive
<
2022-04-20
>
thheller07:04:08

see https://shadow-cljs.github.io/docs/UsersGuide.html#_cursive no need to switch to deps.edn unless you really want to

Baye13:04:20

Hi, Thanks all for your time. Set an SDK (JDK) project settings -> project -> SDK This setting does not exist in Cursive version I have (IntelliJ Ultimate Paid)...but a proper SDK is already set up for the project • deps aliases are active (View -> Tool Windows -> Clojure Deps Clojure Deps does NOT show up View -&gt; Tool Windows -&gt; see https://shadow-cljs.github.io/docs/UsersGuide.html#_cursive no need to switch to deps.edn unless you really want to 

shadow-cljs pom does not run on Terminal (intelliJ)
Now all of this maybe due to the fact I am a newbie...for that I apologize but my problem is still NOT resolved. Interestingly though the reagent app is running OK on the browser: ONLY issue I cannot find how to run the any REPL

thheller13:04:57

did you follow the steps from the docs? I mean create the a new project from existing sources? fixing an incorrectly setup project is much harder than just creating a new one from scratch

thheller13:04:21

and what "does not run" mean?

Baye13:04:55

I tried to follow this but does not work

Baye13:04:37

Also for a normal clojure project, I run the REPL by find an option after right-clocking on the project.core file...for a reagent project I cannot find where to run the REPL anywhere

thheller14:04:11

@sowsoule what does "does not work" mean? was the project created successfully? did you follow the rest of the instructions?

thheller14:04:18

> You can run npx shadow-cljs server inside the Terminal provided by IntelliJ and use Clojure REPL → Remote Run Configuration to connect to the provided nREPL server. Just select the "Use port from nREPL file" option in Cursive Clojure REPL → Remote or configure a fixed nREPL port if you prefer.

Baye19:04:44

> creating the pom file was not working with the cloned project, but works now with the new proejct I created. Thanks again. However, i am still not sure how to run the repl. I don't understand the following instruction: "lojure REPL → Remote Run Configuration to connect to the provided nREPL server. Just select the "Use port from nREPL file" option in Cursive Clojure REPL → Remote ". I don't how to open the repl server port. Second, and my main issue, how do you open the clojure repl, so that if I want to evaluate code and see output in the repl (not the browser)? Appreciate your patience with me.

joshkh15:04:36

my IntelliJ is stuck “Synchronizing Clojure Deps project”. i’m sorry if this has been answered before.. i found a few archived Slack chats but no solution. any ideas? so far i’ve tried invalidating my cache and restarting. • IntelliJ Build #IC-221.5080.210, built on April 12, 2022 • Cursive 1.12.2-2022.1

joshkh15:04:06

i’ve also tried right click deps.edn > Refresh Clojure Deps Project, but the background task gets stuck at Stopping - Synchronizing Clojure Deps Project

tony.kay20:04:06

So the ns parsing is better on the latest EAP, but the indexing of resolved macros seems all hosed. When I tell it to “resolve as” something it seems to not reindex (possibly because I already had told it that resolution before, but it was no longer doing it). Is anyone else experiencing these kinds of “unresolved symbol” warnings in the IDE even though you’ve set the resolution for the macro in question? I’m going to try to invalidate caches and restart, but it has been weird ever since the change to the ns parsing in Cursive.

👍 1
markaddleman22:04:17

The work around us to resolve as something else (I choose none) and then resolve as th coreext definition

tony.kay22:04:14

Yeah, for now I just reverted to the Nov 29th version. That one works as expected. I’ll wait till this stabilizes 🙂

aratare01:04:46

tl;dr is it’s still WIP

cfleming05:04:27

@U0CKQ19AQ Yes, this is something I’m working on at the moment. The issue has been present for a while, it definitely predates the ns parsing stuff, but for some reason it seems to be getting more frequent recently. I still suspect changes in IntelliJ rather than changes in Cursive, since there’s very little code involved on the Cursive side, and most of it hasn’t changed in a long time.

tony.kay15:04:00

I’ll keep an eye out. The Nov 29th release definitely works well for me in 2021.3.2

qmrw23:04:15

Does anyone know if it's possible to get a history (preferably with vi keys) in the nREPL input section?

👀 1
cfleming07:04:11

Tools | REPL | Search REPL History