Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2021-07-16

Channels

#calva
<
2021-07-16
>
Trey04:07:10

any extension recommendations for Emacs-like keyboard shortcuts in VSCode?

deleted04:07:28

this appears to be the most maintained one though https://marketplace.visualstudio.com/items?itemName=tuttieee.emacs-mcx

❤️ 5
Trey16:07:27

thanks for the recommendations! I’ll try out the “awesome” one

partywombat 2
dgb2307:07:26

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?

pez08:07:01

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.

👍 2
p-himik16:02:55

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

pez16:02:51

Thanks, @U2FRKM4TW! I don't undertand why I miss these. I subscribe to them! 😃

👍 1
dgb2307:07:33

To clarify I typically use the Jack-In command to start a REPL

dgb2307:07:19

and just a deps.edn for most of what I do, no other dependecy/build tools or anything like that

deleted17:07:15

I wish there was a command to kill the repl, sometimes I just want to shut it down

pez18:07:38

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.

pez18:07:14

If you started the REPL with Calva, you can press ctrl+c in the jack-in terminal.

pez19:07:26

System exit works too. 😃

practicalli-johnny23:07:00

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.

practicalli-johnny06:07:14

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.

practicalli-johnny06:07:07

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

pez06:07:35

To support starting the REPL process in a terminal, Calva has a command for copying the jack-in command line to clipboard. However, VS Code has neer needed a restart for as long as I have been using it. And also it keeps your terminal sessions between restarts anyway.