Fork me on GitHub
#calva
<
2023-05-08
>
mkvlr07:05:36

morning 👋 I’ve long been wanting to provide clerk instructions for setting up a clerk-show command in calva and got a https://github.com/nextjournal/clerk/pull/393. There’s two remaining questions that I’d appreciate help with: • how can escape backslashes (https://github.com/nextjournal/clerk/pull/393#issuecomment-1439805607) in a custom repl command with the snippet "(nextjournal.clerk/show! \"$file\")" • on emacs I have clerk show bound to option + enter (macOS). Wondering if that’s also a good idea to have a keybinding on calva or would that violate users expectations?

pez07:05:12

Hi! Exciting stuff!

pez07:05:45

The backslash problem needs to be fixed in Calva, I don’t think there’s a way to fix it for an end user as things are now…

mkvlr07:05:46

ah ok, so the command as-is is fine and will stay the same? Easy. 🙃

mkvlr07:05:01

and option + enter seems to be taken by calva already, so certainly that’s not a good binding to use. Any other suggestions for something similar to eval form that’s still free?

mkvlr07:05:38

or are the custom repl command shortcuts not global?

mkvlr07:05:14

it seems they’re local to the custom repl command shortcut only. Is there a way to set up a repl snippet with a global shortcut?

pez08:05:33

Custom Snippet commands get default keybindings if you provide a key:. There are also ways for the user to bind “real” shortcuts: See https://calva.io/custom-commands/#binding-keyboard-shortcuts about this. There is no way to configure the “real” shortcuts in the workspace, afaik.

pez16:05:14

Dear Calva friends. I introduced a regression with connecting shadow-cljs REPLs with v2.0.356. I’ve fixed it in https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.358, please upgrade! • Fix: https://github.com/BetterThanTomorrow/calva/issues/2185https://github.com/BetterThanTomorrow/calva/issues/2184 I’m sorry for the inconvenience this caused you. It was a stupid mistake with me hardcoding a thing and it Worked on My Machine… In this release also a fix for an old problem that I haven’t been aware of until today. ^That^ problem with $file path substitutions in custom command snippets not working on Windows. Thanks for reporting, @mkvlr!

❤️ 6
mkvlr16:05:40

@U0ETXRFEW oh thanks for the super quick fix! 🙏

🙏 2