Close an exiseting SSH tunnel before creating a new one with cider-connect #3536
Unanswered
JMacLulich
asked this question in
Q&A
Replies: 1 comment
-
Created #3537 - let's see what we can do about it! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have had this problem for a long long time.
And with GPT-4 I finally got motivated enough to try and solve it.
My problem is when I cider-connect to a remote host via SSH it creates a tunnel -- that's fine.
Every subsequent connect to a different host uses the same tunnel which is tunneling to the first host.
It's so very annoying, I have to manually tear down the tunnel and re-establish it to connect to the right remote host.
I wanted a cider function that would look for existing SSH connections on the same port and tear them down so that a new one to the right remote host is established.
GPT-4 got me this far, but the var
cider--connections
is not defined (as is maybe others) and I don't know how ot proceed from here.Any advice would be great (my emacs lisp is very basic, because I've actively tried to avoid it).
p.s. if possible I would love it to to host auto-completion the same way
cider-connect
already does, butcider-known-hosts
seems to benil
.Beta Was this translation helpful? Give feedback.
All reactions