calva

pez 2025-12-12T13:02:49.110559Z

Anyone tried REPLTILE? https://open-vsx.org/extension/repltile/repltile-clojure-repl If I understand correctly, it is a Calva extension, making things feel more at home for #cursive users. Doesn’t seem to be available on the VS Code Marketplace, but I guess you can download the VSIX from OpenVSX and install in VS Code. Anyway, if someone tries it, I’m curious about the experience!

Max 2025-12-14T14:21:57.043059Z

I also would be interested to know what the webview repl looks like

clyfe 2025-12-14T14:39:09.898509Z

pez 2025-12-14T19:31:58.803359Z

Looks pretty sweet!

Max 2025-12-14T19:34:12.893659Z

Seems like there's potentially some interesting opportunities to do some more interactive data explore-y stuff there

hrtmt brng 2025-12-12T21:05:08.860599Z

The key binding for paredit.backwardSexp on MacOS has a when condition cursorBeforeComment. Why is this? The key binding only works for me if I remove this part of the condition.

hrtmt brng 2025-12-14T09:38:03.802319Z

This is what confused me.

pez 2025-12-14T09:59:06.834349Z

ctrl+left/right are not supposed to be the Mac bindings for moving by s-expression, alt+left/right are. The default is that Calva repurposes some common VS Code bindings to structural commands. For moving by s-expression, If you disable this default, Calva will use ctrl+left/right instead. (Which didn’t use to be bound by VS Code for anything.)

👍🏼 1
hrtmt brng 2025-12-13T12:27:13.817419Z

This is the default key binding. Option -> works. But Control -> does not work. When I remove the orange part, then Control -> also works. The same for backwards.

pez 2025-12-13T13:15:32.350649Z

It’s the option variants I use, come to think of it. I'm afk. See if the changelog has any clues. I seem to recall something from pretty recently about this.

pez 2025-12-12T21:54:34.119499Z

!calva:cursorInComment || calva:cursorBeforeComment is because backwardSexp doesn’t make any sense in line comments, except in the case where the cursor is exactly before a line comment. Is there something else binding ctrl+left, maybe? You can search in the keyboard shortcuts UI. Thinking it could be something with specificity that somehow gets different when you remove that exception.

seancorfield 2025-12-13T00:09:09.717449Z

It would be cmd+left on a Mac? I bet that conflicts with some default O/S binding. I used to have all sorts of issues on macOS with it hijacking useful key bindings in my apps:unamused: