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)Issue please. I think there may be a lot of crap in the when clauses.
https://github.com/BetterThanTomorrow/calva/issues/3338, sorry I didn't have time to fully flesh it out
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.
@pez filed a ticket: https://github.com/BetterThanTomorrow/calva/issues/3341
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 ™️
aha
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’ll keep trying
I'll make a video
Now I can repro. I was being a bit stupid.
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.