I don’t think it has been changed anything around that in Calva. If you remember when it last worked you can try both with using a Calva from that time, and with using a VS Code version from that time.

sure, that was yesterday. will need to check on my laptop

For reference, current:

Calva version used: v2.0.446
clojure-lsp version used: 2024.04.22-11.50.26
clj-kondo version used: 2024.03.13

hm, must be something else because Calva version on my laptop is the same

And VS Code versions?

Found the issue, it was behind the keyboard

my bad

No problem. Glad it works!

I opened the folder and not the workspace:melting_face:

It’s a quite confusing Ux. Though I do not know if it is possible to unconfuse it. The feature is very nice!

I opened from shell and usually it just works with code-insiders . but this time it didn't so I tried code-insiders .code-workspace and that solved it.

You can use some styling of the titlebar and things to easily see when you’re in the workspace. This is what we use in the Calva project:

"workbench.colorCustomizations": {
    "sash.hoverBorder": "#90B4FE",
    "titleBar.activeBackground": "#DB9550",
    "titleBar.activeForeground": "#131722",
    "titleBar.inactiveBackground": "#db9550d5",
    "titleBar.inactiveForeground": "#13172299"
  },

ohh will have a look at that

thanks for the tuip

tip*

Makes it easy to find using alt+tab too.

But maybe it’s not so common to have 20 VS Code windows open, like I often have. 😃

not so much lol

note, for those color customization's to work you also need this setting: _"window.titleBarStyle":_ "custom"_,_

So, what's a sash ?

The divider between panes that you drag to shrink one and grow another. If you paste that setting as it is, you will quickly see what it is. 😃

:thinking_face:

found it! haha

nice

I’m not sure what can be done about it. Please file an issue and maybe we can figure something out. You can add those to your global gitignore and at least you will not commit the directories to the repo. Though if you have local config that doesn’t work.

Also, if other things permit it, it may work placing the babashka project folder as the first folder in the workspace.

Maybe it can be done with https://blog.agical.se/en/posts/vs-code-runcommands-for-multi-commands-keyboard-shortcuts/. Stringing together jack-in and this command.

will have a look at that tomorrow then

thanks

Do you know what action is needed to press enter in a popup? For instance I trigger an action that creates this input screen at the top but I want it to just auto select and start

What action is it? Maybe it takes an argument and when given one will not pop up anything.

I spent the morning trying everything I could find, my keybindings.json is a mess. Even tried doing it in Joyride without succes. I gave up lol. The command is workbench.action.terminal.join

I ended up doing this btw:

{
  "key":  "shift+ctrl+alt+n",
  "when": "terminalHasBeenCreated || terminalProcessSupported",
  "command": "runCommands",
  "args": {
    "commands": [
      "workbench.action.terminal.focusNext",
      "workbench.action.terminal.join",
    ]
  }
}

if I add :remove-surrounding-whitespace? false to .cljfmt.edn it works but it’s less than ideal for the rest of the formatting

I think I heard that James Reeves is open for adding this kind of formatting to cljfmt. See if you can find an issue in that repo. I place a :rcf keyword inside the closing paren.

I just add a ';' on a line before the closing parens, that keeps formatting stable.

Why would it remove a closing paren? Do you mean it shifts it to the end of the comment block?

Mine look like this

That looks pretty weird, @U02CX2V8PJN 😃

haha how so?

Isn't that normal behaviour?

If I remove the first empty line the trailing parens automatically moves to the end of the last line

I always add a string "title" to my comments for improved readability when I have all code collapsed