> • how to have emacs launch a process that doesn't die when it dies. I'm looking at the detached package though. > I'm away from keyboard, but check out emacs --daemon and emacsclient -nw

I agree with @U7RJTCH6J, there's really no need to exit Emacs 😁

Here's a few suggestions for dealing with REPL in emacs that may or may not be relevant: • Agree with others suggesting emacs should generally be left open and just attach using emacsclient to continue where you left off. • REPLs should also be left open - use something like https://github.com/weavejester/integrant-repl to reload your project. • If you have multiple projects. you can sometimes create a top level project that depends on the other projects and then launch a REPL in this project (so you end up with fewer REPLs). • In some situations use sesman-link-with-buffer to temporarily assign a namespace to a different REPL (good for updating a library namespace from a parent REPL). • You can build many kinds of business and interactive websites entirely on the backed with hiccup and a sprinkling of HTMX and _HyperScript - if you do this then you can you don't need a ClojureScript/shadow REPL at all. • You can add something like this to your .emacs file to start several REPLs at once in a single command:

(defun cider-init ()
  (interactive)
  (find-file "~/code1/project.clj")
  (call-interactively 'cider-jack-in)
  (find-file "~/code2/project.clj")
  (call-interactively 'cider-jack-in-cljs))

(global-set-key (kbd "C-x C-y") 'cider-init)

So the emacs server is going to start the nrepl server independently of the emacs client?

lets see if chat gtp can help

the site is so busy that i can't even upgrade to pro in order to get an answer. It's almost as if a universal flexible query model is going to bottleneck so quickly that it becomes meaningless.

I don't think you need chatgpt for this:slightly_smiling_face: - there's plenty of info on the web.

@UJVEQPAKS i know, it's more to test the waters. Your insights were very helpful. I'm looking into a couple of them more before i ask another question.

I wasn't trying to say that you shouldn't have to exit emacs. Only that you don't have to.

I use a separate emacs for each project I work on. However, I use emacs --daemon when I'm working on a hobby project with a server. It means that my session persists even if I lose my connection. I'll often even use it to run the http server for the project.

I understand, starting emacs as a server and then starting the repl from the client seems to persist the repl server across clients. Which is a big part of what I wanted.

so thanks a ton 🙂

> In my current workflow, I often find that I want to quit emacs, but I don't want to lose the nrpel server in that process Just curious, why do you want to quit emacs rather than just leaving it open?

I do think your centralized nrepl-connection-manager idea is neat.

@U7RJTCH6J, roughly the same reasons that i need to restart my computer, things start to get slow in various points and a restart will seem to improve the situation without having to do a more specific diagnosis as to why. I believe spacemacs suggests restarting after package installs and upgrades as well, though that might not be critical.

@UJVEQPAKS > In some situations use sesman-link-with-buffer to temporarily assign a namespace to a different REPL (good for updating a library namespace from a parent REPL). So for example, you want to update a libraries version, but that lib is currently being used as that's part of a running server, so you can't just bump it without restarting the server. So instead you make a new clj project, with the library set to the newer version, and start a repl, then using sesman-link-with-buffer to attach the namespace in the server to the updated project?

Sort of. Example: You have a REPL open in some code and you spot a bug in a library that you also have the code for: Use sesman-link-with-buffer to evaluate code that you have fixed in a library namespace in your current REPL session.

There is a toolchain by lambda island that i'm looking into before I start trying to build my own thing https://github.com/lambdaisland/launchpad.