Fork me on GitHub
#cursive
<
2021-09-07
>
cfleming08:09:11

Unfortunately I’m not very familiar with WSL (I don’t use Windows) and I don’t really know how IntelliJ’s recent support works either, sorry. Hopefully someone who’s actually using it can chime in and be more useful than me.

folcon13:09:05

I've not had that particular error @U01JPGC1PQQ, my issues with wsl2 have been related to ports. In my experience it's better to boot the repl in wsl2 via terminal for example and then connect to cursive via a remote repl...

folcon13:09:27

Just make sure you open your ports internally and it works fine

DG15:09:17

@U0JUM502E the ports are open, this isn't the issue. The issue is when running the application or the tests, which in that case Cursive has to run a new JVM (and not just connect to the REPL)

DG15:09:57

Are you able to run your application or your tests by using the Run or Debug in Intellij?

folcon15:09:46

Hmm, to be honest I don't run my tests within intellij, I just run them at the command line on wsl2. My application does function fine when I've run it, but it effectively runs in windows if I trigger it with run configuration not wsl2.

folcon15:09:53

So these don't end up being blockers for me, whereas REPL experience is the main thing I care about 😃... Sorry if that's unhelpful!

DG15:09:14

Oh no worries, it's always helpful. Thanks 🙂

steffan10:09:39

@U01JPGC1PQQ I've been running Cursive in WSL2 for some time, by running an X server (VcXsrv) and the Linux version of IntelliJ. There's a little bit of setup to enable X11 forwarding, then you're good to go: https://stackoverflow.com/questions/61110603/how-to-set-up-working-x11-forwarding-on-wsl2

steffan10:09:23

When WSLg is released, running graphical apps such as IntelliJ on WSL should be easier.

folcon15:11:51

Which reminds me I should try this out next chance I get 😃...