Fork me on GitHub
#chlorine
<
2020-04-10
>
mauricio.szabo14:04:01

@fabrao I think I may have a lead on what's happening with goto var definition. Just a question, are you using Atom on Windows, with WSL or without? And Clojure on Windows also with or without WSL?

fabrao15:04:01

@mauricio.szabo I´m using Atom on Windows and I have WSL installed but not active

mauricio.szabo15:04:20

Okay... I think I may have a lead on your problem. Will try to reproduce here 🙂

fabrao15:04:30

What do you think WSL is "infecting" Atom Windows?

fabrao15:04:38

I´m using WSL 2.0

mauricio.szabo16:04:45

Not really, it can be a problem with backslashes / forward slashes on Node + Clojure + Atom. There's a lot of things that can go wrong when you add interops between Java URIs, absolute paths, windows, and Node.JS 😞

seancorfield16:04:07

There is some custom logic in Chlorine (at least, I assume it's still present?) that tries to detect whether you are on the same O/S as your REPL, deliberately to support Atom on Windows talking to a REPL on WSL, and it maps Windows drives to WSL mount points. It should not come into play for Windows talking to Windows tho'...

mauricio.szabo16:04:22

Yes, it is still there on load-file command. I'll try to check if I can reproduce the error on Windows, and if so, if that logic solves the problem

mauricio.szabo18:04:16

Ok, I'm able to reproduce. Will work on a fix

mauricio.szabo19:04:32

@fabrao just one last question: what's the version of Java you're using? Even better: what java -version prints to you?

mauricio.szabo20:04:04

I am amazed: Java returns /C:/.... as the file path... :(

seancorfield20:04:41

I'm surprised about the leading / but otherwise not surprised that it returns / since forward slashes work on both Windows and macOS/Linux in Java.

seancorfield20:04:13

(I suspect that breaks the load-file logic for cross-platform stuff too?)

fabrao21:04:07

@mauricio.szabo Sorry about late response

openjdk version "1.8.0_242"
OpenJDK Runtime Environment (build 1.8.0_242-b08)
Eclipse OpenJ9 VM (build openj9-0.18.1, JRE 1.8.0 Windows 10 amd64-64-Bit Compressed References 20200122_564 (JIT enabled, AOT enabled)
OpenJ9   - 51a5857d2
OMR      - 7a1b0239a
JCL      - 8cf8a30581 based on jdk8u242-b08)

fabrao21:04:59

I observe too that clicking into error line when Exception happens the same problem runs out

mauricio.szabo21:04:06

Yes, it's the same code. Considering that you're the only person who have this problem, I'm thinking it may be a problem with OpenJ9 (by luck, I also installed OpenJ9). I'll change java version and see if changes anything

fabrao21:04:26

I had to switch to OpenJ9 because I use Webstart for using with Cisco stuffs

fabrao21:04:48

let me change to the other java

mauricio.szabo21:04:38

Don't worry, I also use OpenJ9. I'll issue a fix, but probably will open a bug report for OpenJ9 too

mauricio.szabo21:04:19

Ok, its not an issue of OpenJ9 - hotspot does the same thing. I'll fix it...

fabrao22:04:20

@mauricio.szabo I tried with other version of Java and the same problem happen