This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-16
Channels
- # announcements (3)
- # babashka (25)
- # beginners (71)
- # calva (18)
- # clj-kondo (52)
- # cljs-dev (94)
- # cljsrn (12)
- # clojure (33)
- # clojure-europe (52)
- # clojure-nl (2)
- # clojure-uk (27)
- # clojurescript (18)
- # clojureverse-ops (4)
- # datomic (64)
- # deps-new (27)
- # depstar (5)
- # events (5)
- # fulcro (5)
- # graalvm (12)
- # graalvm-mobile (82)
- # helix (2)
- # introduce-yourself (1)
- # juxt (5)
- # lsp (10)
- # malli (7)
- # missionary (1)
- # off-topic (41)
- # pathom (69)
- # pedestal (6)
- # re-frame (4)
- # reagent (8)
- # releases (9)
- # remote-jobs (8)
- # shadow-cljs (3)
- # sql (46)
- # tools-deps (44)
- # uncomplicate (1)
- # vim (83)
this appears to be the most maintained one though https://marketplace.visualstudio.com/items?itemName=tuttieee.emacs-mcx
Not sure if this is a calva or a VSCode question but typically processes in the integrated terminal are killed when closing the VSCode window on macos. I had several instances of REPL processes lingering after I closed VSCode. • am I doing something wrong? • is this something I deal with manually? • is this an issue with VSCode or Calva than can be resolved?
It could be the feature where VS Code detaches and reattaches terminal sessions when closing and reopening a workspace. There might be a setting to disable this. And maybe Calva should have a way to deal with it. To manually kill the jack-in process, press ctrl+c
in the jack-in terminal.
Only as a data point, just stumbled upon this SO question that seems relevant here: https://stackoverflow.com/questions/71011227/calva-how-to-stop-the-repl/71081092
and just a deps.edn for most of what I do, no other dependecy/build tools or anything like that
VS Code + Calva is a good choice! 😃 https://clojureverse.org/t/gnu-emacs-cider-vs-vs-code-calva/7829/26?u=pez
If you started the REPL with Calva, you can jack in again. It will kill the REPL and start it anew. However, if you often have the need to kill the REPL, you might benefit from asking why.
I prefer to run the repl process in a terminal and therefore it's easy to stop or restart the repl regardless of editor. Calva can then connect to this external repl process. If the editor has to restart, it does not affect the running repl process. Therefore it's a more robust approach It's a shame this approach is described in less than positive terms in the Calva docs.
Jack-in adds a few libraries to the command that it calls to start an external repl process and connect. This is the same command, i.e. lein or clojure, that you would run in a terminal. For Leiningen you would add those libraries to the dev profile. For Clojure CLI you would use an alias.
Leiningen already starts nRepl, so the clder-nrepl library is required to allow cider-based editors (Cider, Calva, Conjure) to communicate with the nRepl server. For Clojure CLI, nRepl and cider-nrepl should be added, which I have in several aliases to start the Repl with additional tools such as visual data browsers