Clojurians Log v2

Sounds like the last expression is being evaluated rather than the top level expression. VSpaceCode will do both types of evaluation commands, so maybe there is a different keybinding / command to use with the vscodevim extension. Or just move to the line after the expression and evaluate

Actually Calva doesn’t really have a concept of last sexpression. It will try to find the “current” form.

In Calva, evaluate the current form behaves like evaluate last s-expression when the cursor is after a nested expression but still within a top-level expression

For example, with the cursor on the last closing paren in this expression (- 10 (* 2 3)) , the "evaluate current form" will return 6 using "evaluate top level form" returns 4

So my suggestion to the original question is to use "Calva: Evaluate top level form". Or move to the next line and use "Calva: evaluate current form" which evaluates the top level form it finds behind the cursor.. shouldnt matter how many empty lines there are.

So unless a specific nested form should be evaluated, then use "Evaluate top level form"

Calva will evaluate (* 2 3) if the cursor is before it as well (unless there is a previous sexpr on the same line, which will take precedence.

Good to know. I like the simplicity of current and top form evaluation. The Calva approach seems a simpler than the 8 different command available for Cider 🙂

Great tip to switch to use “Evaluate top level form” instead, thanks :thumbsup::skin-tone-2:

File a feature request about it, @janne.sauvala. Maybe there is a way we can detect the normal mode.

You can also try configuring a custom command for now. Yesterday I pushed a change that makes it easier to get keyboard shortcuts bound to those. There are quite a few predefined ones,, chords starting with ctrl+alt+space and then things like a-`z` and digits and some more. See https://calva.io/custom-commands/

A shortcut something like this might work:

"calva.customREPLCommandSnippets": [
        {
            "name": "Normal mode eval current form",
            "key": "enter",
            "snippet": "$current-form)"
        }
    ]

Also try what is evaluated in normal mode if you have the cursor adjacent before the list.

Thanks, Peter. I can try that also 🙂

I tried vscodevim myself now. I had misunderstood the behaviour some, so that custom command won’t cut it. I noticed that having the cursor on the opening bracket or before it evaluated the form though.

For comparison, in VSpaceCode I use the , e f for the top level form and , e e for last expression, to match the bindings in Spacemacs and SpaceVim

, e e for current expression. 😃

foo
 | bar

foo | bar

Really useful to know about the way current expression works, I like it. Thank you.

There is kind of a disclaimer here: https://calva.io/vim/ & I don't think that's all on :calva: as I have issues with :vim: bindings with other languages on Visual Studio Code. So, TBH if I'm feeling Vimmy I've been using https://liquidz.github.io/vim-iced/ lately & I actually have the Vim plugin disabled in VS Code 😕

I only had to remap Calva Esc key binding to Shift-Esc and all was fine with Calva and VSpaceCode for key bindings. I should add the submitted VSpaceCode key bindings for Calva on the page you mentioned, thank you for the reminder.