Clojurians Log v2

Okay so it had only gotten to that point where calva wouldn't start after I had tried a whole system restore to see if I could just go back to a working state. After a lot of tinkering I got back to a "haywire" but working state, by haywire I mean that the pretty printing isn't working, which at this point isn't a super big deal, but I basically have to manually move to the next line to evaluate more code or else it includes the previous line in my code; before I never had this issue and it would just always newline after evaluating things. The other issue with this right now is that I notice it isn't connecting to my namespace right away. Unless I am imagining things, I believe it used to just jump right into whatever namespace I had it in, but now I seem to have to manually move to a namespace in order to evaluate code from there. I also seem to be having wsl issues that might be related... So it appears that I am coming to permission issues where it won't let me modify the things in this wsl distro, which includes the repl output...... I tried to exit vs code and use sudo chown -R me:me . sudo chmod -R 755 . and then find . -type d -name ".calva" -exec chmod -R 777 {} \; 2>/dev/null in order to reset my permissions but I keep getting the same errors.

It does let met use the repl and make changes to new directories so maybe the solution is just going to be to clone my old project and start on it in a new directory

Also I have this in my settings.json for vs code

"calva.prettyPrintingOptions": {
    
        "printEngine": "pprint",
        "enabled": true,
        "width": 120,
        "maxLength": 50
    }

If you work in a freshly cloned directory. What issues remain?

The repl seems to work but it just isn't inserting newlines

The return of the atom itself is pretty printed, but then the repl itself doesn't insert a newline after the return

See if it is the same with some previous version of Calva.

That solved it - I rolled back one patch to 2.0.498 and now everything works as expected

Thank you!

Oh, oh. Then we have a problem. Thanks for reporting!

I can’t reproduce the problem. Neither on Mac, nor on Windows. But I am not using WSL, so that could be it. What is a small reproduction for you, @wistfulmelodylispfulp?

This issue just in. https://github.com/BetterThanTomorrow/calva/issues/2778 Seems to be with entering a new line at the end of the file. Which I think matches the problems in the REPL Window, where this is what you do all the time (if you use it for repling). I can’t reproduce this one either though on Windows or Mac.

I am experiencing it with WSL, but it also happened on on the windows side of my hard drive as well before rolling back the patch, so I am not sure. Admittedly I have done lots of tinkering to my system in the last 2-3 weeks so it might have been limited to my setup but I don't know what caused it? I am not really sure how best to come up with a reproduction of it honestly.

The haywire was caused by a bug in Calva. It wasn’t os specific. Fixed in v2.0.500.

Wow. From what you describe it seems Calva isn’t starting at all. Very hard to tell if that would be because of those issues with the system, but I wouldn’t guess it’s related. What does “going haywire” mean? Since it all started there, maybe we can get clues from that. Sometimes VS Code itself accrues dirty state that can be quite hard to get rid of. What you could try is to download VS Code Insiders and see if Calva starts there. It’s a totally separate install and their config and state are kept separate.