Twice today the clj-kondo java process has run amok on my machine. Something in the files I am working with today probably triggers it. Anyone else seen that happen?

@pez See this thread: https://clojurians.slack.com/archives/CBE668G4R/p1600900901018900

Might be an issue with the clj-kondo extension or interaction with Calva. Not sure yet. Please install this debug plugin: and keep an issue on the clj-kondo output tab

and report issues to me

Thanks. Using the debugging build now. Let’s hope the java process runs amok again 😃

Clj-kondo process has also been acting up for me. Works fine for a while, then starts eating a ton of CPU. I will try to install the debug plugin when I have time.

Might be a recent interaction with Calva. Source is still unknown, but please monitor the clj-kondo output panel. This is the latest.

I use calva, I jack-in normally, evaluation works great etc. But when I do something wrong and send a snippet that contains something wrong I get quite excessive ouput like this https://gist.github.com/littleli/369b66c1ea822da7f5e5b663484048de Is this expected? It's confusing 😞

@ales.najmann This is expected, and I completely agree. I think @brandon.ringe created an issue where we collected some ideas around how to do this better. Right now I can only find this one though: https://github.com/BetterThanTomorrow/calva/issues/756

@ales.najmann @pez I found this one. Let's use this one and I'll close the other.

https://github.com/BetterThanTomorrow/calva/issues/737

This may be what I focus on next. Hopefully can in the next week or two.

You're great guys 👏

Thanks for mentioning the issue. Helps to see more demand for some issue/improvement so we know what to focus on.

Hello folks. Does anyone have problems with the default key bindings under MacOS? In my case I use calva.loadFile a lot. It’s by default bound to ctrl+alt+c enter but nothing happens when I hit ctrl+alt+c. Any tips on how to get this key binding to work?

Hi @ccidral ! Not sure I follow. What's supposed to happen when you press the first sequence is that vscode shows a message in the status bar saying that it is waiting for the next key press. That's not happening? If so, see if something else binds ctrl+alt+c.

Hi @pez that’s correct, I was expecting to see that message in the status bar, but when press ctrl+alt+c nothing happens (ie: no “waiting” message shows up in the status bar).

I’m running a brand new MacOS Catalina installation. I checked the OS’s keyboard shortcuts but couldn’t find any conflicting shortcut.

If you search for the shortcut in vscode, does that turn up anything but Calva commands?

No, I searched for ctrl+alt+c under Keyboard Shortcuts but it’s all Calva commands.