Open fasfsfgs opened 7 years ago
After reading more attentively https://github.com/boot-clj/boot/wiki/Cider-REPL , I realised that to get the same editing support with Boot as with the plugin's built-in REPL starter, REPL has to be started with cider like
boot cider repl
instead of just
boot repl
.
Hmmm nice!
Do you still need to add a dependency to profiles.clj
in order to get the extension working?
The built-in REPL starter works without problem, even if I completely remove ${HOME}/.lein/profiles.clj
.
Yup. That's one of the benefits of using it. This issue is for those who, for whatever reason, want to connect to an already running nREPL started with boot.
One useful improvement would be the ability to configure the plugin so that it first try connecting to an already running REPL.
Another way to help Boot users would be to provide setting(s) to tell the plugin how to run the REPL. The plugin could eventually let the user specify the entire command line — which would be
boot cider repl
in the case of Boot users.
When we didn't have the ability to run our own nrepl, we used to try connecting to an already running nrepl. But we have to remember that those need to have dependencies configured (at least for lein). So I don't think prioritize already running nrepls make sense.
As for your second point, that would end up being our own nrepl, but run on top of boot instead for lein. For now, we only support lein, but we can try to use lein or boot (depending on what is installed on the users machine).
@avli The point of this issue was to explicit the dependencies required when connecting to an already running nrepl (either using lein or boot), like we used to have in README. I think we should make a page in our wiki for that.
From @pdkovacs at #47:
This is also related with #31.