Which version of Calva?

I notice recent versions of Calva skip the port dialog if it can determine it from the .nrepl-port file (which has always been correct for me).

I am on v2.0.338

I haven’t noticed it, maybe I was in some old version when I tried it last and I was getting the port dialog. Let me see if it’s connecting to the correct port

hmm, for me port in .nrepl-port is not correct because I am trying to port-forward it from k8s pods. Updating .nrepl-port seems to be working fine, thanks

but how does .nrepl-port work? where does it takes the port from? should we still show the port dialog with some default port value selected?

That file is created locally when you start an nrepl server (locally).

There is a Calva setting for prompting even though there is a port.

You can also customize the port file path using a connect sequence and have your repl start script write the port to that file.

If you delete the .nrepl-port file and it isn’t recreated somehow you should still get the prompt without changing settings.

wow, that’s a lot of options 🙂 thanks @U0ETXRFEW I’ll try that setting to prompting

It is mentioned here: https://github.com/BetterThanTomorrow/calva/issues/2113 Might be still an issue.

I have checked it on a minimal project nrepl: 1.0.0 cider-nrepl: 0.28.5 cider/piggieback: 0.5.3 clojure-lsp version configured: latest Calva version used: v2.0.338 Run Jack-in process via deps.end project-type. ps -a show java process. Then ctrl + c in Calva terminal -> ps -a java process still there.

Are you on Linux? Which Calva version are you using?

VS Code running on WSL 2 : Ubuntu 18.04. Calva version used: v2.0.338

ctrl + c worked on v2.0.336

Thanks! Please file an issue.

So far I think this might be a Linux issue. Will test on my fedora box later today.

Ok, thanks

I have the same issue and I use macOs.

macOS: Venture 13.2.1
VsCode: 1.76.2
Calva: v2.0.338

@U0AJQJCQ1 can you repro this issue too?

Should be fixed in 339, please let me know if it is or if it isn't. I couldn't reproduce, but I am pretty sure I found the cause of the problem.

@U0ETXRFEW - I did notice a few times, it wasn't stable though. But I did need to manually kill a zombie java process. I haven't been having it since I updated java to opensdk 19 for the apple chip. Probably unrelated though.

@U0ETXRFEW - Thank you, confirmed that 339 fixed it. I was able to reproduce on 338 just now and it's working great in 339.

Apparently was fixed. 🙏

🙏

You can try to refactor the namespace symbol. Default keybinding is F2 on mac.

thanks. can you tell me the exact name for the command? shft+cmd+p doesn't show anything for refactor namespace symbol or anything close to that.

It’s a general rename refactor. Afk. But look for rename maybe?

'Rename Symbol'. I got there through 'Keyboard Shortcuts', which you can get to through Settings (gear icon at bottom left).

@U0D5RN0S1 thanks, works great.

Here is the error log spam

@U0ETXRFEW

Followed by

This time it started responding again after a while. What I did was cut (ctrl+x) 4 lines of code and pasted it somewhere else in the code.

I did have some issues with formatting/indents/prettyprint and changed the backend for from pprint to calva

Let me try that

pprint had some troubles formatting some macros, calva option have been working so far

Maybe something has changed in clojure-lsp. Try with a previous version.

will try that aswell @U0ETXRFEW

@UM1PCCLNN I don't think that is anything new really. pprint on the server runs in the process and has benefits such as being able to render lazy sequences, but can also fail pretty printing some stuff.

The parinfer extension is unmaintained I think. So it could have some problems with new vscode for sure. I don't see how those clojure-lsp problems could be related. And maybe they aren't, but doesn't look good anyway.

A request being canceled is client(Vscode) cancelling it because is not relevant anymore, usually when you changed the code or did a new request for that, I can't see why is related to parinfer as well

parinfer is what makes the code line out and be on the right indent right?

Maybe something changed in the automatic outlining/indenting code?

I used to be able to just press TAB and all the bindings/expressions in the current Sexp would automatically line up

For some reason this either doesnt work like it did before, changed or is slower

I now need to line up my cursor to the opening paren and press tab

while before I could just do this inside the parens

for some reason the cursor jumps to the end of the file some times

after pressing tab

Here's an example

I have to explicitly move my cursor to just before the opening paren to be able to use TAB for auto indentation

This is with

Calva version used: v2.0.338
clojure-lsp version used: 2023.02.27-13.12.12
clj-kondo version used: 2023.02.17

Could be a result of a change between 336 -> 337. It's Calva doing that, not parinfer (well, could be that both do it, I am not a parinfer user so wouldn't know). I do not understand GIF language, so you are welcome to file an issue using before/after text examples and it might be clearer to me what is not working.

I think I see what is going on in that GIF now, @U02CX2V8PJN. Can you check if this VSIX fixes it: https://output.circle-artifacts.com/output/job/94fa2c17-3e92-4c92-b716-4c72f3846cc1/artifacts/0/tmp/artifacts/calva-2.0.339-2114-toplevel-indent-bug-a7408a29.vsix

Calva had an update to 339 today? It seems solved already?

Yes. I could reproduce it.

Thanks for the quick solve