Fork me on GitHub

I am using the production calva-dev and I noticed that I am unable to use vim mode - if I remember correctly it worked before - I start in normal mode and can switch to insert mode but I can not switch back with esc Anybody else have this —


Let me know if that wiki page helps you, @U054219BT. We probably should add a check for vim mode in Calva.


Thanks that helped I had to change to change the Calva inline setting since my fingers are wed to escape with vim — works fine now


Glad to hear! Yeah, I still sprinkle my files with i and A and such even since it was many years since I used vi, so know what you mean!


Dear channel. I need some help with prioritizing the issues with Calva 2. You can pick up the latest build here: Please give it a few spins on your projects and let me know if you stumble across stuff. I have tried to mark all Calva 2-related issues on Github with the prefix [2.0] so if you file new issues, please follow that pattern. But, as I said, right now it is much a matter of prioritizing. I need to get Calva 2 out, and need help identifying the most important things to fix.

Tomasz Rojek09:05:31

Hi! I have a strange issue, I configure new environment VSCode + Calva and when I start REPL and execute some function it works but when I change that function and run it one more time - the REPL doesn't see that it was changed. Do any one know why it could happen?


Have you re-evaluated the function after changing it?

Tomasz Rojek09:05:12

No I don't. How can I re-evaluate it?


Easiest way is to use the Evaluate top level form command. Place your cursor in somewhere in the function and run that command. (You can either find it in the command palette, or use the keyboard shortcut: ctrl+alt+v space.)

Tomasz Rojek09:05:56

It works, thank you. Is there exist "automatic" way to re evaluate functions after changes?


I don't recall right now... But there might be a setting for re-evaluating the file on save. Not sure I recommend it, though. It is often good to control what is re-evaluated yourself.

Tomasz Rojek09:05:19

I'm new to clojure world and it seems strange to me but I will follow the best practices:)


I'm not an expert, but for me it works best to evaluate on-command. There is a command to evaluate the file as well, which I always start with after having opened a new file. After that, I re-evaluate stuff I change. Also, I don't work very much at the repl prompt. I evaluate stuff in the editor and put stuff inside (comment ...) forms to execute my functions. The top-level commands work in there as well.

Tomasz Rojek09:05:18

How can I execute auto formater from VSCode? Is the auto formater use this guide: ?


You should have Calva Format installed together with Calva, I think. It formats stuff automatically for you, mostly according to that guide. Also the vscode commands for formatting the document will use that formatter. And further the tab key will re-format the surrounding form from where your cursor is.

Tomasz Rojek09:05:54

If I could ask why you decided to split Calva and Calva formater?


I wanted people who use something other than Calva for their REPL to also have a formatter. (But it will be all in one with the next version of Calva because reasons.)

Tomasz Rojek09:05:04

Is it possible to write VSCode plugins in that way that you can disable some functions of it? If yes I think that it is a good direction to make all-in package.


@tomek423 I haven’t looked into this course, but it might be worth looking into if you’re new to Clojure


Or, spend a little bit of time reading up on Repl-driven development.


(I mention this because you say you’re new to Clojure, and in my experience, “getting” RDD is a big part of getting Clojure)

Tomasz Rojek10:05:47

@slipset Thank you. I looked at some videos on about Clojure data structures and there are very good. But I don't see anything about repl-driven development. I definitely have to.


Oh, and welcome 🙂