-
-
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
Boot build tool compatibility #920
Comments
+1 I think we can do better than this : https://github.com/boot-clj/boot/wiki/Cider-REPL |
@pandeiro Sure, I'll take a PR implementing this. Adding boot support has been on my roadmap since the Conj.
Doing a project type check will be trivial ( |
@donmullen Lein has special support for nREPL middleware, which makes the setup simpler there. Not sure what we can do about boot. Guess I'll have to play with it (or someone should dig further into this). |
Similarly to how |
- These things actually parse the banner to get the port and stuff...
@bbatsov I've got a branch with boot support working and the existing tests passing. I haven't added any tests b/c I couldn't find My work is here. Let me know if I should submit the PR as-is or if it needs more work, please? |
@cichli Not sure how that would work, exactly... Would cider, if boot were detected, inject something into build.boot? That seems heavy on the magic to me. Isn't the recommended method, a Or is there another way I'm not seeing? |
@bbatsov Looking at your line comments now; there is one further issue -- anecdotally it seems some projects have a project.clj and build.boot to facilitate use with either tool. Don't know how prevalent that is/will become, but how would you propose dealing with that? Ie, should cider maybe somehow allow the user to specify the jack-in command to use, as C-u cider-jack-in currently allows the user to select a project? Thoughts? |
If both files are present we should prompt the user for input. On Tuesday, January 13, 2015, Murphy McMahon [email protected]
Best Regards, |
OK that would be a completing read for 'lein' or 'boot'? |
Yep. On Wednesday, January 14, 2015, Murphy McMahon [email protected]
Best Regards, |
implement boot support for cider-jack-in, closes #920
The
cider-jack-in
command, hallowed be its name (and shortcut), will unfortunately not boot up a REPL and attach a client to it in projects that use Boot instead of Leiningen. This is unsurprising, given the predominance of lein, but boot support would be nice and, looking into it, the issues at play are simple and mostly confined to nrepl-client.el. Basically, they are:nrepl-project-directory-for
needs to recognizebuild.boot
in addition toproject.clj
files.nrepl-server-filter
would need to adjust its regex to accept both lein's "nREPL server started on..." and boot's "nREPL server listening..." outputsThis would enable barebones support, with users using customization to specify "boot" as
cider-lein-command
and "repl -s wait" ascider-lein-parameters
.However... in the future, perhaps detection by cider for the appropriate defaults for those values on a per-project basis would be convenient to end users.
Question: would a pull request to implement the two immediate simple changes above be welcome? Or, is there any orientation in general on this question?
Thanks
The text was updated successfully, but these errors were encountered: