Lukas Domagala

> Whenever you connect to a REPL, Calva creates a persistent Portal server based on a separate environment (not hosted within the JVM or CLJS or anything inside the project,...

That's the portal client side. You still need a server that sends stuff over. That's why you still need the portal dependency in your repl, even if you have the...

@seancorfield at that point, wouldn't it be simpler to start your own repl and auto-connect to it from calva instead of starting it from calva? Note that I don't want...

I was just reading the docs and this is probably what we need to add to createClient: `{ scheme: 'untitled', language: 'clojure' }`. The `file` scheme apparently ignores untitled.

It's a bit vague, but that was my interpretation of this part: [scheme](https://code.visualstudio.com/api/references/document-selector#document-scheme)

The "client" is just the basic vscode implementation that we add our stuff on top of. The documentSelector we provide to the client determines which files are seen as relevant....

You are right. But speeding up the merge case is easier, because we can use promise.all. The no-merge case can probably be sped up by creating all promises first, but...

If I'm not mistaken clojure-lsp should catch changes to the config files and updated its running-config. Is this also true for the clj-kondo config @ericdallo?

@PEZ what do you mean by "cider gutters"? Googling that gives "unexpected" results ;)

Depends a little bit on which provider. Completions might be OK to merge, but we'd have to play around with it