Fork me on GitHub
#calva
<
2021-01-11
>
pez07:01:20

The fewest step you can achieve is by defining a custom connect sequence, then it becomes ctrl+alt+c ctrl+alt+j enter.

pez07:01:39

A minimum config looks something like so:

"calva.replConnectSequences": [
    {
        "name": "my-app",
        "projectType": "Leiningen",
        "cljsType": "none",
        "menuSelections": {
            "leinAlias": null,
            "leinProfiles": ["test", "dev"]
        }
    }
]
Depending on what profiles you have and such.

bastilla12:01:34

Stupid question here: How can I stop a nREPL? (and/or disconnect?)

pez13:01:15

Have you started it using Calva, @bastilla?

bastilla13:01:43

I did. And when I right-click the option to stop is disabled. Thing is, I obviously programmed an endless loop. So I have constant output and cannot stop it. So I closed Calva altogether. But I guess there must be a better solution.

ryan echternacht13:01:11

^ That was the best solution I found. Or to kill the underlying render proceses

ryan echternacht13:01:01

I think pez said if your loop is printing, then it’ll build up so much in the buffer that interrupting doesn’t do much

bastilla13:01:57

🙂 Thanks. Ok, so I better care for that endless loop to get things going again. Merci.

Stefan13:01:06

Hehe that’ll teach ya’ 😜

pez15:01:47

So, if you start the REPL using Jack-in, the preferred way to kill it is to hit ctrl+c in the jack-in terminal. Also re-running jack-in will work. But as @ryan072 says, if there is a lot of stuff buffered for the output window, a reload of the vscode window will be necessary. The vscode command Developer: Reload Window should work for that.

ryan echternacht16:01:50

Thanks @pez. I didn't realize there was a command for that.

ryan echternacht16:01:54

@bastilla fwiw, for advent of code, I would put short sleeps in my code so that I could watch it run and kill it when I had seen enough steps. Depending on your use case, that may or may not help

ryan echternacht16:01:32

it has the advantage of not blowing out the calva buffer with mass text tho

afry17:01:31

Hello Calva users and maintainers! As you may be aware, I'm currently engaged in a project called Startup in a Month, which is a project I'm embarking on for all of 2021 to make 12 startup in 12 months, all with Clojure and ClojureScript. I'm practically brand new to the language, but I'm banking on the quick learning curve and all the benefits of the language to give me a big productivity boost. You can learn more about it here: https://startupinamonth.net Anyway, being new to the language, I'm also new to the tools and REPL. I'm a first-time Calva user, and the maintainers of the library (looking at you @pez) may be interested to watch me make my first steps with it. These two stream recordings in particular have a lot of footage of me hitting my head in the dark as I try to figure things out 😅https://www.twitch.tv/videos/864853522https://www.twitch.tv/videos/865807336 Hope you find this useful for user-testing research! And hope to see you in the stream 🙂

❤️ 2
pez17:01:50

Thanks! ❤️ Haven’t checked it out yet, but generally this is stuff that is hard to get at for finding out where the Ux problems are. Will definitely look at these!

alexmiller21:01:22

hey just wanted to say I looked at Calva today for the first time in a long time and wanted to say kudos - super easy to install and get started

❤️ 5
calva 4
bringe21:01:16

As Peter said, thanks! It always feels good to hear the effort put into something is really paying off.

pez21:01:17

Oh, thanks, @alexmiller! It is super great to hear this from someone who really knows what makes a good Clojure dev environment. Yesterday I watched you demo Clojure to a bunch of Java devs and you mentioned Calva in the passing, also revealing that you hadn’t tried it. So I was about to reach out asking that you give it a spin so that we can get your input. Quite amazing that you beat me to it. 😃

alexmiller21:01:36

I was connected to a repl in <10 minutes, so that was pretty easy

metal 3