-
-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Opening a new connection to an existing nREPL server #1300
Comments
So, the auto-completion you get in |
The auto completion has always been enough for me to connect to a previously started server. Is there anything you think it lacks? |
@bbatsov - That's exactly what I had in mind. @Malabarba - In my experience which is now a few weeks stale, server/port auto complete only works on localhost. The context in which I would find a "clone" command interesting would be duplicating a connection (including reusing the SSH tunnel if possible) to another machine. |
I see, then it's certainly a worthy feature. I didn't know it only works with localhost. |
If we do this the command will end up doing too much IMO. Finding the balance is always hard. Btw, this is related to the portscanner feature request as well. |
I've found it convenient in the past to have severan nREPL connections to a single nREPL server. Especially when messing with expressions that take a while to evaluate. At present it's easy enough to start a new nREPL server (C-c M-j) but without inspecting the resulting nREPL server buffer for a host/port it's not trivial to open a new REPL buffer connected to the same server.
Obviously something I'm fully capable of working around, but it'd be a nice addition.
The text was updated successfully, but these errors were encountered: