I'm sure that Calva is gaining user share 😁I think the really interesting thing will be finding out where it is taking share from... I'm going to guess from IntelliJ/Cursive. It's not a zero-sum game, of course, the "pie" is growing...

One data point is that Calva Spritz already has almost 3000 installs.

you gained at least one tough holdout, to be sure.

I hope a growing pie is most of it. But there's churn in IntelliJ, things stop to work that worked just fine and after some hits of that, people start to consider the alternatives.

This was a very good idea that you came up yesterday when we talked @U0ETXRFEW, and now you already implemented it! I'm super happy with this. Next week I will test live share with my colleagues again, to see whether there are any live-share related Calva issues remaining and hopefully also address them. 🎉 Thanks a lot Peter!!!

And I only came up with the idea because I misunderstood something you said. 😃 Let's hope it actually solves the problem!

I think you'll need to remap x to paredit forward delete somehow. Not a VIM user here so don't know how it works... Maybe https://calva.io/vim/ can offer some starting point. (If not, we should fix that.)

I have got it working by remapping, but I have not been able to make it aware of the file type, so that ‘x’ still works with other languages, filetypes. According to this https://code.visualstudio.com/docs/languages/identifiers clojure is not identified. The setting i am using is : { “before”: [“x”], “commands”: [ { “command”: “paredit.deleteForward” } ], “when”: “editorLangId == clojure”, } but the ‘when’ is not working

If it is the same when clauses as with regular vscode, you could try copying the when clause for Calva’s default keybinding and try that.

Hmmm, no, Calva also does editorLangId == clojure. Very strange that it is not defined. Calva code relies on it all over.

Thanksss Peterr !!!

We both read that list sloppily, @U04T3JCE9GX. Clojure is there. 😃 I think it is that when clauses are not available when defining VIM keybindings. You might get away with something like this, though, in the vscode regular keybindings file:

{
        "key": "x",
        "command": "paredit.deleteForward",
        "when": "editorTextFocus && editorLangId == clojure && vim.active && vim.mode == 'Normal' && !inDebugRepl && !suggestWidgetVisible && !renameInputVisible && !findInputFocussed && !replaceInputFocussed && !isInEmbeddedEditor && !hasOtherSuggestions && !hasSnippetCompletions && !hasMultipleSelections && !hasNonEmptySelection && !editorReadonly"
    },

Thankssss, I’ll have a go. Yes, I have seen it is there now.

I would bet it was not before

Its hard for me to believe we both missed it

Maybe they put it there and we are gaslighted? 😃

just rechecking clojureverse is smarter than chatGPT 😜

I have just tested your regular keybinding, and it workssss 👍 Thanksss

It was a joint effort between ChatGPT and Copilot mostly. 😃

I saw a video today that cursive does that, I do not know, use cursive, but just in case that functionality code can be copied, reused

Cursive is not open source, I think. Besides, it would spoil the postwalk fun. 😀

No idea what issues Reagent introduces or if this lib is any good to begin with. But have you considered https://github.com/green-coder/html-to-hiccup ? I'd say 44 GitHub stars sounds promising enough to be worth taking a look. The codebase is tiny, but depends on InstaParse. Not sure how much weight InstaParse brings in.

Worth taking a look at. Even if we don’t have the requirement that it should be cross platform. We could use parse-html from npm and do a postwalk on that AST.