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
cider-connect-cljs: make server, port and build configurable #2563
Comments
I guess we can have just some default server and port settings for all connect commands, not just the cljs connect. |
That would be even better, of course. 👍 |
Thinking a bit more about this it should probably be a default endpoint or something like this, as we currently do. Have you seen |
Thanks, didn't know about It works fine, although I still have to select the endpoint and the build before having a working CLJS REPL. But it's a good workaround, thank you! |
If you set it in .dir-locals to one option it basically comes to pressing RET, RET, which is not a big deal I would guess. One solution without adding an extra config would be to allow |
I am already setting |
The default should be most recently used endpoint. I guess it depends on the completion framework that you use. It works correctly for me with IDO. |
I am on |
I still think that adding a default endpoint is kind of orthogonal to the known endpoints (and in line with other config options with have). Even if you have one candidate but you have to select it all the time it can get somewhat annoying. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding! |
Request
When I use
cider-connect-cljs
to connect to ashadow-cljs
nREPL server, I always need to manually select theserver
, theport
and thebuild
, which for a project have always the same values every time.Possible solution
It'd be nice if I can set the default
server
,port
andbuild
in.dir-locals.el
, just as I do for the CLJS REPL type withcider-default-cljs-repl
for instance.Current alternative
As of now, I just do it manually. It's not a blocking issue, of course, it's just something to speed up the initial setup of the environment.
The text was updated successfully, but these errors were encountered: