Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2021-07-24

Channels

#calva
<
2021-07-24
>
pinkfrog14:07:52

Is calva going to support parainfer. Currently, vscodevim really does not play well with calva. For example, typing o in normal mode breaks the parens.

pez15:07:00

If you disable Calva's auto formatting, it won't interfere with Parinfer.

pinkfrog15:07:32

When I uncomment the =when= condition, the shortcut doesn’t work. 

{"key": "ctrl+, b",
        "command": "paredit.backwardSexp",
        // "when": "calva:cursorBeforeComment && editorLangId == 'clojure' || calva:keybindingsEnabled && editorTextFocus && !calva:cursorInComment && !config.calva.paredit.hijackVSCodeDefaults && editorLangId == 'clojure' && editorLangId == 'clojure' && paredit:keyMap =~ /original|strict/"
    },
However, the when condition is a direct paste of the default values. When I go with the default key binding ctrl-(up-arrow), everything goes fine. But with the changed key shortcut, it doesn’t work.

pez17:07:02

Do you maybe have better luck if you change the shortcut from the the UI for it?

pinkfrog05:07:31

No luck though.

pinkfrog08:07:29

To add more details, I found, if I remove the 

!config.calva.paredit.hijackVSCodeDefaults
part. then it works again.

pinkfrog08:07:54

The weird thing is, with the settings UNtouched, the default key binding ctrl-<- works.

pez08:07:56

Thanks for updating! Please file an issue about this.