This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (7)
- # beginners (30)
- # boot (6)
- # calva (24)
- # cider (8)
- # clj-kondo (8)
- # cljs-dev (16)
- # cljsrn (8)
- # clojure (60)
- # clojure-italy (19)
- # clojure-mexico (6)
- # clojure-nlp (2)
- # clojure-uk (11)
- # clojurescript (36)
- # datomic (11)
- # hoplon (1)
- # juxt (2)
- # kaocha (1)
- # keechma (13)
- # nrepl (1)
- # off-topic (51)
- # reagent (7)
- # rewrite-clj (17)
- # robots (7)
- # shadow-cljs (2)
- # sql (4)
- # testing (1)
- # tools-deps (11)
- # vim (12)
@slack1038 please file an issue about the powershell quoting, if you haven’t. The more details, the better for the reproduction.
@slack1038 Regarding closing the connection with the non-jack-in scenario (connect), I am not sure what you mean with “the window”. Here’s what happens when you connect:
1. An nrepl client is created
2. The nrepl client connects to the nrepl server and gets a session
3. The session is cloned and stored as Calva’s
clj session (this is used for all editor clj repl things)
clj session is cloned.
5. A repl window is created backed by this latest clone of the session.
When you close the repl window, its repl session is closed, but Calva’s
clj session (created in 3) remains open until Calva is deactivated or a new connection is performed.
In this scenario Calva does not create any java processes so can’t really leave any zombies behind either.
@pez ah okay that clarifies it for me then and i mean the repl window sorry. then i guess the zombie issue can be closed 🙂 regarding the quoting issue i will open for it the a issue
And jack-in really is: 0. Start a vscode task that starts the project with the nrepl server and cider dependencies injected.
And from there, as long as vscode keeps its promises regarding tasks, we shouldn’t be leaving zombies behind.
@slack1038 time for a voice chat/hang out trying to investigate the quoting some together? My Mac really can’t handle running Windows 10 in Virtual Box…
Just throwing around ideas with a colleague, does VSCode support some kind of "distribution"? Where I can create a custom VSCode distribution (.exes, dmgs, whatever) with some plugins pre-installed & configured and share them?
@dominicm not really but there is a extension where you can share your setup with multiple vscodes installations
@pez training. I want to just give people a fully loaded vscode setup with no room for "oh, I already have a config and this is breaking it"
vscode has this “project settings” thing that might override the user settings. (Or might not, I am not sure which has precedence)