-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
Make it possible to associate a project folder with any connection #1217
Comments
Yes, this seems most sane. Also, when you first A more sophisticated option would be to let users name the connections somehow. This is the tricky part. |
There's already functionality to rename connections, btw. I think that setting this on boot won't be that hard either. |
This command should mostly be used with connections created using `cider-connect`.
So, the bulk of the work regarding is done. The only outstanding tasks are:
|
I think this works more or less well in it's present form, so I'll close this issue. |
Right now our primitive algorithm that matches local project directories to nREPL connections is pretty limited. It works only for connections that were started using
cider-jack-in
, because it maps a project dir to a connection at boot time. It also cannot handle very well situations when several projects are mapped to the same connection. All this makes it hard to work with several connections, as often you have to switch manually between them.One way to improve this is to able to associate a project directory with any connection, using an interactive command, you can invoke at any time. That is simple solution that would solve the bigger part of this issue. In rare cases when some project is mapped to two connections we can opt to dispatch to the default connection (meaning business as usual). //cc @Malabarba
The text was updated successfully, but these errors were encountered: