calva 2026-11-04

There appears to be a small regression in the latest update: by default, when the cursor is in a comment, killSexpBackward removes the entire comment rather than reverting to "delete word backwards" mode. It can be fixed by changing the when clause context on the keybinding for killSexpBackward to:

calva:keybindingsEnabled && paredit:keyMap =~ /original|strict/ && !calva:cursorInComment && (calva:replInputFocused || (editorTextFocus && editorLangId == 'clojure'))
(this is also a simplified version of the default when clause context. The default one has tons of redundant clauses)

🙏 1

Issue please. I think there may be a lot of crap in the when clauses.

I never flesh my issues out. 😃 Not true, but if I have the context and I think I will take the issue, then I do not spend time authoring it much. In this case I have enough context and I think it will be me taking this one since I was the one causing it and all.

One more quirk in the output view I just discovered on mac: if you're focused on the output view and you hit the default keybinding for "Toggle maximize editor group" (cmd+k cmd+m), it seems like the cmd+m also gets passed to the window manager, causing the window to get minimized. This doesn't happen in normal editor views.

I can’t reproduce this. Neither in Cursor, nor in Code. Not saying it is not happening for you, just that I am flying a bit blind.

Try it in a floating non-main window? I just tested, and it doesn't happen in the main window

cmd+m minimizes. cmd+k cmd+m toggles group maximizing. On my machine ™️

vscode has so many bugs with floating windows

Yeah specifically it shows up in split floating windows where one of the splits is the output view

I still can’t repro,

1

I’ll keep trying

I'll make a video

Now I can repro. I was being a bit stupid.

lol i'm sure you were being differently smart 😄

❤️ 1

The nature of the issue may indicate that I will not be able to fix it easily, but we will see.

Maybe there is a mention in vs code issues about it.