Hi. I have a problem with compiling code, the issue is that for some reason calva or vs code keeps compiled jars open. After restarting vs code, the issue resolves itself. Its very inconsistent so I don't have any steps to reproduce the issue
Hi! That’s very inconvenient. And quite strange. Calva doesn’t ever concern itself with the compiled jars. That’s for the repl process to care about. Are you using Jack-in? If so Calva and VS Code are holding on the the repl process and could explain why a restart of VS Code helps. Then you could see what results you get if you start the repl outside of VS Code and connect to it from Calva. It would surprise me if Calva is causing this. I don’t see an opportunity for Calva to even do it. But I have been wrong a lot of times in my life.
Yes I am using jack-in. Another problem which I have noticed and might be relevant. When I press f12 to navigate to the source code of a function and I try editing something I get the message: "Cannot edit in read-only editor". The strange thing is that I dont see the path to the file. Its like I am navigated to a previously compiled dependency. The only way for me to edit inside is to manually navigate to the file, ctrl+alt enter it and then f12 works as expected and I can do anything I want inside